APRS Packet Errors for E20OTK-9 (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
20251009004926E20OTK-9>APOTC1,HS3RXX-5*,qAR,HS1AL-1:!1445.rʲ*A14.1V 24C Yaris 7557 Lopburi
20251009005027E20OTK-9>APOTC1,WIDE1-1,qAR,HS1AL-1:!LSrq0035.96EP 14.0V 24C Yaris 7557 Lopburi
20251009005028E20OTK-9>APOTC1,HS3RXX-5*,qAR,HS1AL-1:!1445.44Nrʲ*A14.Y24C Yaris 7557 Lopburi
20251009005444E20OTK-9>APOTC1,HS5NMF*,qAR,HS1AL-1:!1445.49N/10& *028/026
20251009005752E20OTK-9>APOTC1,WIDE1-1,qAR,HS1AL-1:!1447.41NLr*064/035
20251009010027E20OTK-9>APOTC1,HS3RXX-5*,qAR,HS9CEL:!1447.86N16pԲ?s3.8V 24C Yaris 7557 Lopburi
20251009010134E20OTK-9>APOTC1,HS3RXX-5*,qAR,HS1AL-1:!1448.15N/10&)*092/020
20251009010150E20OTK-9>APOTC1,HS3RXX-5*,qAR,HS1AL-1:!1448.13N/100)E>061/011
20251009010202E20OTK-9>APOTC1,HS3RXX-5*,qAR,E22KKC-7:!144)r10036.99E>048/007
20251009010235E20OTK-9>APOTC1,HS3RXX-5*,qAR,HS1AL-1:!Lr6N1003)*A13.5V 24C Yaris 7557 Lopburi
20251009010235E20OTK-9>APOTC1,HS3RXX-5*,qAR,HS1AL-1:!Lr6N1003)*A13.5V 24C Yaris 7557 Lopburi
20251009010334E20OTK-9>APOTC1,WIDE1-1,qAR,HS1AL-1:!1448.28N/100)*328/009
20251009010404E20OTK-9>APOTC1,WIDE1-1,qAR,HS1AL-1:!Lr5N/1003)*263/007
20251009010404E20OTK-9>APOTC1,WIDE1-1,qAR,HS1AL-1:!Lr5N/1003)*263/007