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
20250330200719HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@302006z1ӓ r10040.63ErAR lopburi T=32° H=53% P=1008
20250330203808HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@302037z1447.0)040.63E000g000t090r...p...P...h53L‚b00 AR ɥ T=32° H=53% P=10
20250330205333HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@302053z1447.03N/1r*Ilopburi T=32° H=53% P=1008
20250330210858HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@302108z1ӓ r1004ɚErAR lopburi T=32° H=53% P=1008
20250330212413HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@302123z1447.03N/10040.6Qz:00t090r...p...P...h5&‚b00 AR lopburi T=31° H=53% P=1008
20250330212422HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@302124z1447.03N/100r*Ilopbu 31°*1008