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
20250806230749HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71)41.67E# L&i 37C APRS LOPBURI DIGI WAD KHEA HMIB
20250807004017HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/1004Lɺ* 12.3V 37C APRS LOPBURI DRTKHEA HSR(
20250807014726HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!14N/10041Sr 38C Ab=A UI%DIGI WAD KHEA HMIB
20250807015548HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1ӓr10041.67E# 12.3APRS L%UI%DIGI WAD KHEA HMIB
20250807022923HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/1004Lɺ* 12.3V 38C APRS LOPBURR"%%WAD KHEB5% 
20250807032114HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!14r10041.Sr 38C APRS LOPBURI RTKHEA*J
20250807034440HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!14N/10041.67E# 12.3V 38C APRS LOPBURI DIGI WAD )HMIB
20250807044315HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!144r10041.67E# 12.3V 39C APRS LOPBUR"%%WAD KHEA HMIB
20250807045140HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/1004Lɺ* 12.2V 39C APRS LOPBURR"%%WAD KHEPB5IB