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
20251217194738HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@171946z1ӓ r1004ErAR lop T=31°B45% P=1010
20251217200132HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@172000z1447.03N).63E_000/000g000t089r...p. rrB4b10100L000 AR lopburi U H=44%1010
20251217200141HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@172001z1ӓ r1004ErAR lop T=31° H=44% P=1010
20251217211905HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@1721L447.03N/10040.63E_000/000g87r...p...P...h44b10100L00Ilopburi T=30° H=44% P=L
20251217220523HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@L447.03N/10040.63E_000/:00t086r...p...P...h45b1011Ilopburi T=29° H=45% 1011
20251217222102HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@172220z1447.03N/10040ɚ}00/000gt086r.....P...h45b10110L000 AR lop] T=29° OSS101L
20251217230731HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@172306z1ӓ r10040.Ilop] 29° H=46% POL
20251217232259HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@172322z1447.03N).63ErAR lopburi T=28° H=S1011
20251217235356HS1AL-1>AESPG4,TCPIP*,qAC,T2HAKATA:@172447.03N?Lr*Ilopburi T=28° H=48% P=1012
20251218000918HS1AL-1>AESPG4,qAR,HS0TK-1:@180008z1447.03N/100r*}00/000g000t084r...p...P...h47b10120L000 AR lopburi T=28° H=47% P=1012