APRS Packet Errors for G4MDP-2 (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
20260209113922G4MDP-2>APAT81,WIDE1-1,qAR,G4MDP-13:!5050.35N/00024.99W[/A=000000G4MDP JiM
20260209114003G4MDP-2>APAT81,WIDE1-1,qAR,G4MDP-13:!5050.35N/00024.99W[/A=000000G4MDP JiM
20260209114113G4MDP-2>APAT81,WIDE1-1,qAR,G4MDP-13:!5050.35N/00024.99W[/A=000000G4MDP JiM
20260209114153G4MDP-2>APAT81,WIDE1-1,qAR,G4MDP-13:!5050.35N/00024.99W[/A=000000G4MDP JiM
20260209114302G4MDP-2>APAT81,WIDE1-1,qAR,G4MDP-13:!5050.35N/00024.99W[/A=000000G4MDP JiM
20260209114421G4MDP-2>APAT81,WIDE1-1,qAR,G4MDP-13:!5050.35N/00024.99W[/A=000000G4MDP JiM
20260209114535G4MDP-2>APAT81,WIDE1-1,qAR,G4MDP-13:!5050.35N/00024.99W[/A=000000G4MDP JiM
20260209115031G4MDP-2>APAT81,WIDE1-1,qAR,G4MDP-13:!5050.35N/00024.99W[/A=000000G4MDP JiM
20260209120045G4MDP-2>APAT81,WIDE1-1,qAR,G4MDP-13:!5050.35N/00024.99W[/A=000000G4MDP JiM