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
20260731103449N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260731113452N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260731123451N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260731133451N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260731143441N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260731153449N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260731163449N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260731203451N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260731213449N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260731223447N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260731233443N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260801003442N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260801013450N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260801023446N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260801033444N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260801043452N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20260801053452N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260801063451N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20260801073449N3HYM-5>ID,qAR,LU9DCE:!3918.87N/07737.07W
20260801083446N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260801093443N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W