APRS Packet Errors for HS1AL-1 (last 6 hours)

This table contains packets in which findU has detected an error. This is an automated system, no manual checking of these packets has been done. Most common cause of this is mistakes in entering the latitude/longitude into hard-coded digis, or positions of 0/0. If packets of yours appear here, and you have looked at it carefully and cannot find the error, look again. I've been watching these error messages in my log, and believe my parser is reasonably correct. Go get the APRS spec to be sure. If you have done that, and are CERTAIN the packet is a legal APRS packet, then it is possible that there is an error in my my parser. Only email me if you are absolutely, positively certain...ask yourself, would I bet $100!

time (UTC)Packet
20251215131145HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@151311zLӓ r1004ɚErAR lopburi T=34° H=36%1011
20251215131145HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@151311zLӓ r1004ɚErAR lopburi T=34° H=36%1011
20251215132700HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@151326z1447.03N)r*}00/000g000t093r... rrB7b10L&b00 AR l ɥ T=34° H=37% P=1012
20251215142859HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@151428~Lӓ r1004ErAR lopburi T=33° H=39I1012
20251215142859HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@151428~Lӓ r1004ErAR lopburi T=33° H=39I1012
20251215163228HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@151631z1ӓ r10040.6z:00t090r...p...P. 0120L0Ilopburi T=32° H=43% P=1012
20251215163238HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@MLӒ447.03N/10040.63ErAR lopb 32° HO*1012
20251215182051HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@MLz1447.0&)r*Ilopburi T=31° HOS1011