APRS Packet Errors for 2M_RPTR (last 6 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
20260209103251W0WTN-10>APDW17,qAR,N9LID-10:;2M_RPTR *111111z4454.50N/09707.50WmPHG5230146.850MHz -060 Watertown 2M Repeater
20260209110252W0WTN-10>APDW17,qAR,N9LID-10:;2M_RPTR *111111z4454.50N/09707.50WmPHG5230146.850MHz -060 Watertown 2M Repeater
20260209113251W0WTN-10>APDW17,qAR,N9LID-10:;2M_RPTR *111111z4454.50N/09707.50WmPHG5230146.850MHz -060 Watertown 2M Repeater
20260209120251W0WTN-10>APDW17,qAR,N9LID-10:;2M_RPTR *111111z4454.50N/09707.50WmPHG5230146.850MHz -060 Watertown 2M Repeater
20260209123251W0WTN-10>APDW17,qAR,N9LID-10:;2M_RPTR *111111z4454.50N/09707.50WmPHG5230146.850MHz -060 Watertown 2M Repeater
20260209133251W0WTN-10>APDW17,qAR,N9LID-10:;2M_RPTR *111111z4454.50N/09707.50WmPHG5230146.850MHz -060 Watertown 2M Repeater
20260209140252W0WTN-10>APDW17,qAR,N9LID-10:;2M_RPTR *111111z4454.50N/09707.50WmPHG5230146.850MHz -060 Watertown 2M Repeater
20260209143251W0WTN-10>APDW17,qAR,N9LID-10:;2M_RPTR *111111z4454.50N/09707.50WmPHG5230146.850MHz -060 Watertown 2M Repeater
20260209150252W0WTN-10>APDW17,qAR,N9LID-10:;2M_RPTR *111111z4454.50N/09707.50WmPHG5230146.850MHz -060 Watertown 2M Repeater