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
20251208192809HS1AL-1>AESPG4,TCPIP*,qAC,T2HK:@081927z144 r10040.63ErAR lopburi T=28° H=42% P=1011
20251208200712HS1AL-1>AESPG4,TCPIP*,qAC,T2HK:@0447.03N/10040.63E_000/000g000t083r...p...P 0110L000 AR lopburi T=28° H=42% P=1LL
20251208202544HS1AL-1>AESPG4,qAR,E27ASY-2:@082025z144 r10040.63E_000/000g000t083r...p...P...h42b10110L000 AR lopburi T=28° H=42% P=1011
20251208204613HS1AL-1>AESPG4,TCPIP*,qAC,T2HK:@082045z144 r10040.63ErAR lopburi T=27° H=42% P=1011
20251208204704HS1AL-1>AESPG4,TCPIP*,qAC,T2HK:@0820447.03N/10040.63E_000/000g82r...p...P...h42b10110L000 AR lopburi T=28°% P=1011
20251208214439HS1AL-1>AESPG4,qAR,E27ASY-2:@082447.03N/10040.63E_000/000g000t081r...p...P...h43b10110L000 AR lopburi T=27° H=43% P=1011
20251208224311HS1AL-1>AESPG4,TCPIP*,qAC,T2HK:@’447.03N/10040.63ErAR l uri T=27° OS1012