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
20260126202005N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260126212013N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260126222013N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260126232010N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260127012004N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260127022014N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260127032011N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260127042009N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260127052008N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260127062004N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260127072013N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260127082014N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260127092013N3HYM-5>ID,qAR,N3HYM-9:!3918.87N/07737.07W
20260127102011N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260127112010N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260127122007N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260127132015N3HYM-5>ID,qAR,W3ND-7:!3918.87N/07737.07W
20260127142004N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W
20260127191948N3HYM-5>ID,qAR,PU2XTC-4:!3918.87N/07737.07W