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
20251018020413HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1ӓr10041.67E# 12.3V 39C APRS LOPBURI DIGI WAD KHEA HMIB
20251018023739HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N)r* 12.2V 39C APRS LOPBURI DIGI WAD KHEA HMIB
20251018034431HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.Sr10041.67E# 12.3V 39C APRS LO%UI%DIGI WAD KHEA HMIB
20251018040114HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/100Lɺ* 12.3V 39C APRS LOPBURI DIGI WAD KHEA HMIB
20251018045121HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/10041Sr 40C APRS LOPBURI DIGI WAD KHEA HMIB
20251018045943HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447Sr10Sr* 12.2V 40C APRS LOPDIGI WAD KHEA HMIB
20251018065009HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N)r* 12.3V 41C APRS LOPBURI DIGI WAD KHEA HMIB
20251018070655HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71)r* 12.3V 41C APRS LOPBURI DIGI WAD KHEA HMIB