APRS Packet Errors for DO2TO-1 (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
20260209102743DO2TO-1>APRSMC,TCPIP*,qAR,DB0FRO-12:!5218.83N/01426.89E>#Uwe on Tour/B=100/A=000272
20260209105744DO2TO-1>APRSMC,TCPIP*,qAR,DB0FRO-12:!5218.83N/01426.89E>#Uwe on Tour/B=100/A=000315
20260209115819DO2TO-1>APRSMC,TCPIP*,qAR,DB0FRO-12:!5218.83N/01426.89E>#Uwe on Tour/B=100/A=000279
20260209122833DO2TO-1>APRSMC,TCPIP*,qAR,DB0FRO-12:!5218.83N/01426.90E>#Uwe on Tour/B=100/A=000305
20260209125851DO2TO-1>APRSMC,TCPIP*,qAR,DB0FRO-12:!5218.83N/01426.89E>#Uwe on Tour/B=100/A=000285
20260209132909DO2TO-1>APRSMC,TCPIP*,qAR,DB0FRO-12:!5218.83N/01426.89E>#Uwe on Tour/B=100/A=000262
20260209142942DO2TO-1>APRSMC,TCPIP*,qAR,DB0FRO-12:!5218.84N/01426.90E>#Uwe on Tour/B=100/A=000262
20260209153319DO2TO-1>APRSMC,TCPIP*,qAR,DB0FRO-12:!5218.86N/01426.90E>#Uwe on Tour/B=080/A=000171
20260209154621DO2TO-1>APRSMC,TCPIP*,qAR,DB0FRO-12:!5218.83N/01426.93E>#Uwe on Tour/B=076/A=000236
20260209160403DO2TO-1>APRSMC,TCPIP*,qAR,DB0FRO-12:!5218.82N/01426.89E>#Uwe on Tour/B=070/A=000308
20260209161605DO2TO-1>APRSMC,TCPIP*,qAR,DB0FRO-12:!5218.83N/01426.94E>#Uwe on Tour/B=065/A=000243