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
20251224031928HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@240319z1ӓ r10040.63E_000/000g000t0N&. ..P...h41b10100L000 AR lopburi T=34° H=41%1010
20251224042111HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@240421z1447.03N/10040.63E_0z:00t095r...p...P...h39b1009b00 AR lopburi T=35° H=39% P=1009
20251224045248HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@240452z1447.03N/100r*Ilopburi T=35° H=38%Պ
20251224065545HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@447.03N/10040.63ErP*bɥ T=37° H=32% P=1006
20251224072628HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@240726z144 r10040.63E_000/000g000t100r...p...P...h32b100b00 AR lo T=37° H=32% P=1006
20251224084354HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@2408447.03N/10040.63E_000/000g000t101r...p... k0060L000 AR lopbuZ38° H=31006