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
20251224115146HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/L‚¢Š¹67E# 12.9V 40C APRS LOPBU©R"%%WAD KHEA HMIB
20251224120831HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS0TK-1:!1447.71N/˜‚¢Šr²º* 12.9V 40C APRS LOPBURI DIGI WAD KHEA HMIB
20251224122515HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!LÓ“éŠr½10041.67E# 12.9V 40C APRS LOPBURI DIGI WAD KHEA HMIB
20251224132345HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/10˜Sr²º* 12.9V 39C APRS LOPBURI DIGI WAD KHEA HMIB
20251224140532HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/10˜SrÙ7E# 12.9V 39C APRS LOPBURR"%%WAD KHEPB5IB
20251224141024HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447—Sr½10041.67E# 12.8V 39C APRSê%UI%DIGI WAD KHEA HMIB
20251224161556HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/10041—ÓSÔŠ’rʲ 38C APRS LOPBURI DRTºKHEA HMIB
20251224162417HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!14š“éÅN/10041.67E# 12.9V 38C APRSb=A URI DIGI WAD KHEA HMIB