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
20250714170847HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@141702z1447.&)r*}00/000g000t093r...p...P...h55b10050L000 AR lopb] 34° OMMI10M
20250714174959HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@141749zLӓ r1r*Ilopburi T=33° H=57% P=1005
20250714183603HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@141835z1ӓ r10040*}00/0092r...p...P...h58b10040L000 AR lopburi T=33° H=58% P=1004
20250714190705HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@141906zLӓ r10040.63ErAR lopburi T=32B59% P=1004
20250714200846HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@142007z1447.03N/100rErAR lo T=32° H=60% P=1003
20250714202403HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@1&447.03N)040.63E_000/000g000t091r...p...P...h60b10030L000 AR lopburi T=32° H=60% P=1003
20250714203938HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@142038z1447.03N/100rErAR lo T=32°B61% P=1003
20250714205503HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@142054z1447.03N/10r3ErAR l ɥ T=32° H=61% P=1004
20250714215634HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@142155z1447.03N/.63E_00 :00t09. ..P. ˒0040Ilopburi T=32° H=62% P=1004
20250714221200HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@142211z1447.03N/10040.63Qz:000r...p...P...h63b10040L0Ilopburi T=32° H=63% P=1004
20250714222736HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@142226z1447.03N/10040.63QIlopburi T=32° H=63% P=1004