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
20250402033351HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/1‚¢Šr²º* 12¾M¢’APRS LOPBURI DIGI WAD KHEA HMIB
20250402034214HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!14š“éÅN/10041.ÓSÔŠ’rª² 4¦(ARS LOPBURÍ"%%WAD KHEA HMIB
20250402043227HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.7Lê)‚‚¢Šr²º* L&©² 43(AIMLOPBURI DIGI WAD KHEA HMIB
20250402044910HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.Sr½10041.67E# 12.5V 43C APRS LOPBURI DIGI WAD KHEA HMIB
20250402051415HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447—Sr½10041.67Q$Š’rª² 43C APRS LOPBURI DIGI WAD KHEA HMIB
20250402052236HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/1004Lɺ* 12.5V 42C APRS LOPBURI"%%WAD KHEA HMIB
20250402053109HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/10041—ÓSÔŠ’rª² 4¦(AIMLOPBURI DIGI WAD KHEA HMIB
20250402054802HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/1004Lɺ* 12.5V 43C APRS LOPBURI"%%WAD KHEA HMIB
20250402065534HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.7Lê)‚‚¢Šr²º*L&©² 44(AIMLOPBURI DIGI WAD KHEA HMIB
20250402081047HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/1‚¢Šr²º* 12¾M¢šAPRS LOPBURI DIGI WAD KHEA HMIB