APRS Packet Errors for HS6YHE-7 (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
20261026165410HS6YHE-7>APAT51,WIDE1-1,qAR,HS6YHE-3:!1646.49N/10117.01˘‚‚z‚‚‚ző000367aprs tracker expert
20261026180647HS6YHE-7>APAT51,WIDE1-1,qAR,HS6YHE-3:!L““‰Ęr˝10117.01Ev000/000/A=000374aprs tracker expert
20261026182515HS6YHE-7>APAT51,WIDE1-1,qAR,HS6YHE-3:!1›““‰Ęr˝10117.01Ev000/000/A=000370aprs tracker expert
20261027174309HS6YHE-7>APAT51,WIDE1-1,qAR,HS6YHE-3:!1646.49N/10117.0LQ‚‚z‚‚‚ző000370aprs tracker expert
20261027204851HS6YHE-7>APAT51,WIDE1-1,qAR,HS6YHE-3:!1646.49N/˜ŠŠşr‚’*ŮÁ00/000/A=000370aprs tracker expert
20261028163716HS6YHE-7>APAT51,WIDE1-1,qAR,HS6YHE-3:!1646.49N/LŠŠşr‚Š*ŮÁ00/000/A=000374aprs tracker expert