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
20250712031233HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@120311zӓ r10040.63E_000/00NL. ..P...h54b10030L000 A*bɥ T=32° H=54% P=1003
20250712053120HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@120530z1447.03N/r*}00/000g000t095r...p...P...h47b10030L000 AR lopburi T=35° H=47% P=1003
20250712054644HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@120546z1447.03N/1004r*}00/0:00t095r ..P...h47b10030L000 AR lopburi T=35° H=47% P=1003
20250712061748HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@120617z1447.03N/1004r*Ilo T=35° H=46% P=1003
20250712073450HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@120734z1447.03N/10040.z:00t098r...p...P...h44b10020L000 AR lopburi T=36° H=44% P=1002
20250712075016HS1AL-1>AESPG4,qAR,HS0TK-1:@120S447.03N/10040.63E_000/000g000t098r...p...P...h44b10020L000 AR lopburi T=36° H=44% P=1002