APRS Packet Errors for HS3YJK-9 (last 24 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
20260801010258HS3YJK-9>AESPT4,HS5NMF*,qAR,HS6AU:!14ML)¢rAÅ0103.46E>093/000/A=000029Indy Tracker
20260801011933HS3YJK-9>AESPT4,HS5NMF*,qAR,HS0TK-1:!145rššr½10059.67E>136/005/A=000068
20260801023319HS3YJK-9>AESPT4,HS5NMF*,qAR,HS1AL-1:!1451¾r½10100.93E>083/043/A=000127Indy Tracker
20260801035554HS3YJK-9>AESPT4,HS5NMF*,qAR,E20ZNR-1:!1450.53NP10107.76Q’¢ºz‚‚‚zõ000144Indy Tracker
20260801040159HS3YJK-9>AESPT4,HS5NMF*,qAR,HS1AL-1:!1450.5Lê)‚Š‚ºr¢š*ù277/029/A=000150
20260801052123HS3YJK-9>AESPT4,HS5NMF*,qAR,HS1AL-1:!1451.14NP10103—Ó*ù000/000/A=000045Indy Tracker