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
20260316201950N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260316212000N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260316221957N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260316231956N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260317001954N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260317011951N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260317021959N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260317031957N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260317041958N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260317051955N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260317061954N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260317071952N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260317081953N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260317091953N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260317101954N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260317111951N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260317122000N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W