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
20250411034721	HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.Sr½10041.67E# 12.3V 39C APRS LOPBURI DIGI WAD KHEA HMIB
20250411040405	HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/1˜¢Š¹67E# 12—&šÊAPRS LOPBURI DIGI WADZ!HMIB
20250411050235	HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.Sr½10041.67E# 12.3V 40C APª*b=A UI% DIGI WAD KHEA HMIB
20250411062609	HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447—Sr½10041.67E# 12.3V 41C APRS LOPBURI DIGI WAD KHEA HMIB
20250411065222	HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!144›éŠr½10041.67E# 12.3V 41C APRS LOPBURI DITºKHEA ¤SR(
20250411073320	HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.7Lê)‚‚¢Šr²º* L&i² 43(AIMLOPBURI DIGI WAD KHEA HMIB
20250411075006	HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!LÓ“éŠr½10041.67E# 12.3V 41C APRS LOPBURI DIGI WAD KHEA HMIB
20250411084017	HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/1‚¢Šr²º* 12.&¢’AP©*b=A UI%DIGI WAD KHEA HMIB