APRS Packet Errors for HS3RXX-1 (last 168 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
20261026023515HS3RXX-1>APOTW1,WIDE1-1,qAR,HS3RXX-3:!1448.32N/10036.18E_000/0ʢuH
20261026024718HS3RXX-1>APOTW1,WIDE1-1,qAR,HS1AL-1:!1448.32N/10036.18E_000/0:00t083P000b10192OTW1
20261026025231HS3RXX-1>APOTW1,WIDE1-1,qAR,HS1AL-1:!1448.32)r*}00/000g000t083P000b10194OTW1
20261026025845HS3RXX-1>APOTW1,WIDE1-1,qAR,HS1AL-1:!1448.32N/1003r*}00/000g000t083P000b10192OTW1
20261026031633HS3RXX-1>APOTW1,WIDE1-1,qAR,HS3RXX-3:!1448.32N/1͊* *L2OR
20261026032858HS3RXX-1>APOTW1,WIDE1-1,qAR,HS3RXX-3:!1448.32Ś)&L082Š&
20261026033820HS3RXX-1>APOTW1,WIDE1-1,qAR,E27ASY-2:!1448ir10036.18E_000/000g000t082P000b10191OTW1
20261026035705HS3RXX-1>APOTW1,WIDE1-1,qAR,HS1AL-1:!1448.32N/100r*}00/000g000t082P000b10186OTW1
20261026060425HS3RXX-1>APOTW1,WIDE1-1,qAR,HS3RXX-3:!1448.31N/10036.1}0+SUUH
20261026075357HS3RXX-1>APOTW1,WIDE1-1,qAR,HS3RXX-3:!1448.32N/10036.1}zʂuH
20261026084601HS3RXX-1>APOTW1,WIDE1-1,qAR,HS0TK-1:!1448.32NLr*}00/000g000t081P000h00b10180OTW1
20261026084654HS3RXX-1>APOTW1,WIDE1-1,qAR,HS1AL-1:!1448.32N/10036.18Qz:00t081P000h00b10180OTW1