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
20250823040611HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS0TK-1:!1447.71N/‚‚¢Šr²º* 12.2V 38C APRS LOPBURI DIGI WAD KHEA HMIB
20250823050042HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!144“éŠr½10041.67E# 12.2V 37C APRS LOPBU©)"%%WAD KHEA HMIBà
20250823050442HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!144“éŠr½10041.67E# 12.3V 37C APRS LOPBURI DIGI WAD KHEA HMIB
20250823051306HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!14š“éÅN/10041—ÓSÔŠ’r’² ±APRS LOPBURI DIGI WAD KHEA HMIB
20250823061150HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!144“éŠr½10041.67E# 12.3V 39C APRS LOPBURI DIGI WADZ!HMIB
20250823071017HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.7Lê)‚‚¢Šr²º* L&i² 39(AIMLOPBURI DIGI WAD KªHMIB
20250823082542HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.Sr½10041.67E# 12.2V 38C APRS LO%UI%DIGI WAD KHEA HMIB
20250823094159HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/10041ɺ* 12.3V 39C APRS LOPBURI Tê%WAD KHEA HMIB