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
20250918161737HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/10041.Sjr 38C APRS LOPBURI DIGI WAD KHEA HMIB
20250918161737HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/10041.Sr 38C APRS LOPBURI DIGI WAD KHEA HMIB
20250918165103HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N)r* 12.2V 38C APRS LOPBURI DIGI WAD KHEA HMIB
20250918175754HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!14r10041.67E# 12.3V 38C APRS LOPBURI DIGI WAD KHEA HMIB
20250918181437HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N)r* 12.3V 37C APRS LOPBURI DIGI WAD KHEA HMIB
20250918183119HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N)r* 12.3V 37C APRS LOPBURI DIGI WAD KHEA HMIB
20250918183941HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71)41.67E# 12.2V 38C APRS LOPBURI DIGI WAD KHEA HMIB
20250918193811HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.L)r* L&i 37C APRS LOPBURI DITKHEA HMIB
20250918200316HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71)r* 12.3V 37C APRS LOPBURITu%WAD KHEA HMIB
20250918201136HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!14r10041.67E# 12.3V 37C APRS L%UI%DIGI WAD KHEA HMIB
20250918202819HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.L)r* 12.3V 37C APRS LOPBURI DIGI WAD KHEA HMIB