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
20251119161309HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@1NLS447.03N/10040.63ErAR lopburi T=29° H=41% P=1015
20251119174546HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@191744z1447.03N/1r*_000/000g000t08..p...P...h41b10140L000 AR lopburi T=28° H=41% P=1014
20251119184750HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@191846z1447.03N/10040.63AIlopburi T=28° H=40% P=1013
20251119190320HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@191902z1447.03N/L63ErAR lopburi T=28° H=40% P=1013
20251119194935HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@191948z1447.03N/10r3E_000/000g000t083r...p...P...h40b10130L000 AR lopburi T=28° H=40% P=1013
20251119203559HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@192034z1447.03N/100rE_000/0:00t082r...p...P...h41b10130L000 AR lopburi T=27° H=41% P=1013
20251119205135HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@192050z14ӓ r10040.63ErAR lopburi T=27° H=41% P=1013
20251119210654HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@192105z1447.03N/.63E_000/000g000t082r...p...P...h41b10130L000 AR lopburi T=27° H=41% P=1013
20251119212224HS1AL-1>AESPG4,TCPIP*,qAC,T2INDY:@192121z1447.03N/100rE_000/000g000t082r...p...P...h42b10130L000 AR lopburi T=27° H=42% P=1013