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
20251008222050	HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!14š“uŠr½1˜¢Šr²º*# 12.3V 36C APRS LOPBURI DIGI WAD KHEA HMIB
20251008230236	HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.›Lê)‚‚¢Šr²º* 12.3V 36C APRS LOPBURI DIGI WAD KHEA HMIB
20251008230237	HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.›Lê)‚‚¢Šr²º* L&i² 36C APRS LOPBURI DITºKHEA HMIB
20251008234428	HS3RXX-5>APOT21,HS5NMF*,WIDE2-1,qAR,HS1AL-1:!1447.Sr½10041.67E# 12.3V 36C APRS LOPBURI DIGI WAD KHEA HMIB
20251009004122	HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!144“éŠr½10041—ÓSÔŠ’rš² 36C APRS LOPBURI DIGI WAD KHEA HMIB
20251009005839	HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N—L‚¢Šr²º* 12.3V 36C APRS LOPBURI DIGI WAD KHEA HMIB
20251009005843	HS3RXX-5>APOT21,HS5NMF,WIDE2-1,qAR,E27ASY-2:!1447.71N/100Sr²º 12.3V 36C APRS LOPBURI DIGI WAD KHEA HMIB
20251009015734	HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N)‚‚¢Šr²º* 12.3V 37C APRS LOPBURI DIGI WAD KHEA HMIB
20251009022237	HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.·Lê)‚‚¢Šr²º* 12.3V 36C APRS LOPBURI DIGI WAD KHEA HMIB
20251009023059	HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.?Lê)‚‚¢Šr²º* 12.2V 37C APRS LOPBURI DIGI WAD KHEA HMIB