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
20251009150444HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.7Lê)‚‚¢Šr²º* 12.2V 38C APRS LOPBURI DIGI WAD KHEA HMIB
20251009150445HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.Sr½10041.67E# 12.2V 38(AIMLOPBURI DIGI WAD KHEA HMIB
20251009150446HS3RXX-5>APOT21,HS5NMF*,WIDE2-1,qAR,HS1AL-1:!1447.71N/10˜Sr²º* 12.™šÂAPR©1=A UI%DRTºKHEA HMIB
20251009153951HS3RXX-5>APOT21,HS5NMF*,WIDE2-1,qAR,HS1AL-1:!144“éŠr½10041.67E# 12.3VšÂAPRS ¦%UI%DITºKHEA HSR(
20251009161136HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/1¢Šr²º* 12.3V 38C APRS LOPBUª"%%WA¢Z!HMIB
20251009161957HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N)‚‚¢Šr²º* L&I² 38C  %5b=A UI%DIGI WAD KHEA HMIB
20251009182519HS3RXX-5>APOT21,WIDE1-1,WIDEYF,qAR,HS1AL-1:!1447.7Lê)‚‚¢Šr²º* 12.2V 37C APRS LOPBURI DIGI WAD KHEA HMIB
20251009192348HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N?L‚Ñ1.67E# 12.2V 37C APRS LOPBURI DIGI WAD)ªHMIB
20251009202218HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/10041.67¢$ŠÉ.3V 37C APRS LOPBURI DIGI WAD KHEA HMIB