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
20251224113408HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@2S447.03N/10040.63E_000/000g000t099r...p rrB6b10070L000 AR lopburi T=37° H=36% P=1007
20251224120525HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@241205z1447.03N/Lr*}00/000g000t097r...p... k0070L000 AR lopburi TO& H=38% Պ
20251224122054HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@241220z1447.03)040.63EP*ɥ T=36° H=38% P=10
20251224125133HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@241251z1ӓ r10040.63E_000/000g000t096r...p...P...h39b10080L000 AR ɥ T=35° H=39% P=1008
20251224130658HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@2413447.03N/10040.63E_000/000g96r...p...P...h39b10080L000 AR lopburi T=35° H=39% P=1008
20251224142424HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@241424z1447.03N/10040.63QIlopburi T=35° H=39% P=1
20251224143949HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@241439z1ӓ r10040.63ErAR lopburi O H=39%1008
20251224152609HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@2415447.03N/10040.63E_000/000g000t095r...p...P...h0080L000 P*bɥ T=34° H=39% P=100
20251224161216HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@241612z1447.03N/10040.63E_00 :00t094 ..P...h39b10080L000 AR lopburi T=34° H=39% 1008
20251224165841HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@2S447.03N/10040.63ErAR lo T=33°*1008