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
20250530033925HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/100Sr* 12.3APRS LOPBURI DIGI WAD KHEA HMIB
20250530035608HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!144r10041Sr 38C APRS LOPBURI DIGI WAD KHEA*J
20250530044616HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.7L)r* 12.3V 39C P%5b=A UI%DIGI WAD KHEA HMIB
20250530050259HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/10Sr* 12.3V 39C APRS LOPBURR"%%WAD KHEA HMIB
20250530051942HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/10041.Sr 39C APRS L%UI%DIGI WAD KHEA HMIB
20250530053629HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/10Sr* 12.&APRS %UI%DTKHQPB5% 
20250530061818HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/10041.67Q$2.3V 40C APRS LOPBURI DIGI WAD KHEA HMIB
20250530064325HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/10041.Sr 40C APRS LOPBURI DIGI WAD KHEA HMIB
20250530084027HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/1r* 12.3V 41C APRS LOPBU"%%WAZ!HMIB