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
20251229123642HS1AL-1>AESPG4,qAR,E27ASY-2:@291236z1447.03N/10040.z:00t094r...p...P...h34b10090L000 AR lopburi T=34° H=34% P=1009
20251229132305HS1AL-1>AESPG4,qAR,E20TWR-1:@291322z1447.03N/10040.z:00t093r...p...P...h34b10090L000 AR lopburi T=33° H=34% P=1009
20251229133839HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@2913447.03N/Lr*Ilopburi T=34° H=33I1009
20251229140923HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@291408z1447.03N/10040.6z:00t092r...p...P...h35b10090L000 AR lopburi T=33° H=35% P=1009
20251229142503HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@291424zLӓ r10040.IlopburQ32° H=35% P=1009
20251229144026HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@291439zLӓ r10040.z:0ʒ..p. rrB3b10090LIlopburi T=33° H=33% POL
20251229152653HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@NLM&447.03)r*}00/000g000t090r....P...h35bL000 AR lopburi T=32° H=35% POL
20251229154209HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@291541zLӓ r10040.z:0ʊ..p. rrB6b10Lb00 AR lopburi T=32° H=36% P=1010
20251229162844HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@291628z1447.03N/10040.6QIlopburi31° H=3I1010
20251229164403HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@2NL447.03N/10040.63E_000/000g089r...p. rrB0b10100 AR lo T=31° H=40% P=1010
20251229164413HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@2916&7.03N/163ErAR ɥ T=31° H=39% P=1010