APRS Packet Errors for N3HYM-5 (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
20250508073729N3HYM-5>ID,qAR,W3ND-7:!3918.87N/07737.07W
20250508083724N3HYM-5>ID,qAR,W3ND-7:!3918.87N/07737.07W
20250508093732N3HYM-5>ID,qAR,W3ND-7:!3918.87N/07737.07W
20250508103725N3HYM-5>ID,qAR,W3ND-7:!3918.87N/07737.07W
20250508113727N3HYM-5>ID,qAR,W3ND-7:!3918.87N/07737.07W
20250508123731N3HYM-5>ID,qAR,W3ND-7:!3918.87N/07737.07W
20250508164343N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250508174345N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250508184347N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250508194350N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250508204352N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250508214352N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250508224351N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250508234350N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250509002352N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250509012347N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250509022350N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250509032352N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250509042356N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250509052350N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250509062354N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W