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
20251017143011HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/1r* 12.3V 39C APRS LOPBURI DIGI WAD KHEA HMIB
20251017150337HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!14N/10041.67E# 12.3V 39C APRS LOPBURI DIGI WAD KHEA HMIB
20251017162722HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447Sr10041.6S2.3V 39C APRS LOPBURI DIGI WAD KHEA HMIB
20251017163543HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,E22KKC-6:!ӓr10041.67E# 12.3V 39C APRS LOPBURI DIGI WAD KHEA HMIB
20251017172553HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/10Sr* 12.3V 38C APRS LOPBURI DIGI WAD KHEA HMIB
20251017180739HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!14N/10041Sr &APRS LOPBURI DIGI WAD KHEA HMIB
20251017182422HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447Sr10041.6S2.2V 38C APRS LOPBURI DIGI WAD KHMIB
20251017184108HS3RXX-5>APOT21,HS5NMF*,WIDE2-1,qAR,HS1AL-1:!1447.71)41.67E# 12.3V 38C APRS LOPBURI DIGI WAD KHEA HMIB
20251017184927HS3RXX-5>APOT21,WIDE1-1,WIDE2-1,qAR,HS1AL-1:!1447.71N/167E# 12&APRS LOPBURI DIGI WAD KHEA HMIB