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
20251218222159HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@182221zӓ r10040.63ErAR lopburi O H=44% P=1010
20251218233912HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@18&447.03N)r*}00/000g000t084r...p.. .h47b10100L000 AR lopburi U H=47%1010
20251218233922HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@182338z1ӓ r10040.63ErAR lopburi O& H=47% P=1010
20251219005709HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@190056z14 r10040.63E_000/000g000t086r ..P...h44b10110L000 AR lop] 30° H=44% P=1011
20251219011247HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@1z1447.0&)40.63E_000/000g000t086r... rrB4b10LLb00 AR l ɥ T=30° H=44% P=1011
20251219014343HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@1N447.03N/10040.63E_000/0:00t087r. ..P...h4&0L000 AR lopburi T=30° HO*1012
20251219034738HS1AL-1>AEi94,TCPIP*,qAC,T2HAKATA:@19&447.03N/10040.63ErAR lopb 32° HO&*1012
20251219041837HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@190417z1447.03N/1004*Ilopburi T=33° H=37% P=1012