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
20251206203616HS1AL-1>AESPG4,TCPIP*,qAC,T2HK:@062035z1447.03N/1r*}00/000g000t087r...p...P...h48b1Lb00 AR lopburi T=30° H=* P=1010
20251206205659HS1AL-1>AESPG4,TCPIP*,qAC,T2HK:@062056z1447.03N/1.63E_000 :00t087r...p...P...h48b10100L000 AR lopburi T=30° H=48% P=L
20251206213606HS1AL-1>AESPG4,TCPIP*,qAC,T2HK:@062135z1447.03N/L63ErAR lopburi T=30° H=49I1011
20251206223329HS1AL-1>AESPG4,TCPIP*,qAC,T2HK:@062233z1447.03N/10040*}00/000g000t086r...p...P...h50b10110L000 AR lopburi T=29° H=50% P=1011
20251206233314HS1AL-1>AESPG4,TCPIP*,qAC,T2HK:@062332z14ӓ r10040.*}00/000g000t085r...p...P...h51b10120L000 AR lopburi T=29° H=51% P=1012