APRS Packet Errors for HS3RXX-5 (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
20250709214434HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/10041.Sr 37C APRS LOPBURI DIGI WAD KHEA HMIB
20250709220117HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/10041.Sr 37CP%5b=A UI%DIGI WAD KHEA HMIB
20250709220939HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/L1.67E# 12.3V 37C APRS LOPBURI DIGI WAD KHEA HMIB
20250709233314HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/L1.67E# 12.3V 37C APRS LOPBURI DIGI WAD KHEA HMIB
20250709234134HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.7L)r* 12.3V 37C APRS LOPBURI DIGI WAD KHEA HMIB
20250710004008HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/100Sr* 12.&APRS LOPBU%%WAD)HMIB
20250710005716HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71)r* 12.2V 37C APRS LOPBURI DIGI WAD KHEA HMIB