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
20250913142714HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@131427z1447.03N/10040ɚ}00/000g000t091r...p...P ˂0100L000 AR lopburi T=32° H=6I1010
20250913152912HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@131M447.03N/10040.63ErAR lopburi T=32° H=61% P=1009
20250913161525HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@131S447.03N/10040.63E_000/000g000t090r...p...P..ˊ0090L000 AR lopburi T=32° H=61% P=1009
20250913163104HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@131630z1447.03N/Lr*Ilo T=32° H=62% P=1009
20250913171727HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@131717z1447 r10040.63ErAR lopburi T=31° H=64% P=1009