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
20251207221517HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!14š“éÅN/10041.67E# 12.3V 35C AP©*b=A UI%DIGI WAD KHEA HMIB
20251207235546HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!14Ó“éŠr½10041.67E# 12.2V 35C APRS LOPBURI DIGI WAD)ªHMIB
20251208000409HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!14Ó“éŠr½10041.67E#L&i² 35C APRS LOPBURI DIGI WADZ!HMIB
20251208003733HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447—Sr½10041.67E# 12.3V 35C APRSê%UI%DIGI WAD KHEA HMIB
20251208003734HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447éŠ9½10041.67E# 12.3V 35C APR*b=A UI%DIGI UKHEA HMIB
20251208013118HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71§)‚‚¢Šr²º* 12.3VšªAPRS L%UI%DIGI Wa-!HMIB
20251208013942HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/10041.6SÔŠ’rš² 35C APRS LOPBURI DIGI UKHEA HMIB
20251208022308HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447—Sr½10041.67E# 12.3V 35C APRSê%UI%DIGI WAD KHEAª*J