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
20250703031629HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.Sr/10041.67E# L&I 36C APRS LOPBURI DIGI WAD KHEA HMIB
20250703033311HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N)r* 12.2V 36C APRS LOPBURI DIGI WAD KHEA HMIB
20250703034134HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447Sr10041.67E# 12.3V 36C APRS LOPBURI DIGI WAD KHEA HMIB
20250703041459HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447Sr10041.67E# 12.3V 36C APRS LOPBURI DIGI WAD KHEA HMIB
20250703061951HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.L)r* L&i 38C APRS LOPBURI DITKHEA HMIB
20250703064507HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/10041Sr 38C APRS LOPBURI DIGI WAD KHEA HMIB
20250703065329HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!Lӓr10041.67E# 12.2V 38C APRS LOPBURI DIGI WAD KHEA HMIB
20250703071012HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/10041.67Q$r 37C APRS LOPBURI DIGI WAD KHEA HMIB
20250703081702HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/10041.Sr 38C APRS LOPBURI DIGI WAD KHEA HMIB
20250703083347HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/167E# 12&APRS LOPBURI DIGI WAZ!HMIB
20250703084207HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/1004LE# 12.3V 38C APRS LOPBURI DIGI WAD KHEA HMIB