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
20250826181534	N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250826191532	N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250826211539	N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250826221536	N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250826231534	N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250827001532	N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250827021532	N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250827091541	N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250827101540	N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250827111541	N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250827121538	N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250827131538	N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250827141535	N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250827151546	N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20250827171544	N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W