APRS Packet Errors for DB4MV-3 (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
20260209115709DB4MV-3>APRSGW,TCPIP*,qAR,DB4MV-3:!4806.43N/01104.67E[On Tour test#DB4MV-3/B=100/A=001969
20260209122725DB4MV-3>APRSGW,TCPIP*,qAR,DB4MV-3:!4806.43N/01104.67E[On Tour test#DB4MV-3/B=100/A=001969
20260209125735DB4MV-3>APRSGW,TCPIP*,qAR,DB4MV-3:!4806.43N/01104.67E[On Tour test#DB4MV-3/B=100/A=001969
20260209132750DB4MV-3>APRSGW,TCPIP*,qAR,DB4MV-3:!4806.43N/01104.67E[On Tour test#DB4MV-3/B=100/A=001969
20260209135806DB4MV-3>APRSGW,TCPIP*,qAR,DB4MV-3:!4806.43N/01104.67E[On Tour test#DB4MV-3/B=100/A=001969
20260209142821DB4MV-3>APRSGW,TCPIP*,qAR,DB4MV-3:!4806.43N/01104.67E[On Tour test#DB4MV-3/B=100/A=001969
20260209145836DB4MV-3>APRSGW,TCPIP*,qAR,DB4MV-3:!4806.43N/01104.67E[On Tour test#DB4MV-3/B=100/A=001969
20260209152851DB4MV-3>APRSGW,TCPIP*,qAR,DB4MV-3:!4806.43N/01104.67E[On Tour test#DB4MV-3/B=100/A=001969
20260209155906DB4MV-3>APRSGW,TCPIP*,qAR,DB4MV-3:!4806.43N/01104.67E[On Tour test#DB4MV-3/B=100/A=001969
20260209162921DB4MV-3>APRSGW,TCPIP*,qAR,DB4MV-3:!4806.43N/01104.67E[On Tour test#DB4MV-3/B=100/A=001969
20260209165936DB4MV-3>APRSGW,TCPIP*,qAR,DB4MV-3:!4806.43N/01104.67E[On Tour test#DB4MV-3/B=100/A=001969
20260209172951DB4MV-3>APRSGW,TCPIP*,qAR,DB4MV-3:!4806.43N/01104.67E[On Tour test#DB4MV-3/B=100/A=001969