APRS Packet Errors for VE3PLF-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
20260209132657VE3PLF-1>APN383,VE3RSB*,WIDE2-1,qAO,VA3CQC-1:!4307.14NT07914.94W#PHG6460
20260209135502VE3PLF-1>APN383,VE3RSB,WIDE2*,qAR,KC2WBX-2:!4307.14NT07914.94W#PHG6460
20260209142729VE3PLF-1>APN383,VE3RSB*,WIDE2-1,qAR,KC2WBX-2:!4307.14NT07914.94W#PHG6460
20260209145455VE3PLF-1>APN383,VE3RSB,WIDE2*,qAO,VA3CQC-1:!4307.14NT07914.94W#PHG6460
20260209153025VE3PLF-1>APN383,VE3RSB*,WIDE2-1,qAR,KC2WBX-2:!4307.14NT07914.94W#PHG6460
20260209155457VE3PLF-1>APN383,VE3RSB,WIDE2*,qAO,VA3CQC-1:!4307.14NT07914.94W#PHG6460
20260209162825VE3PLF-1>APN383,VE3RSB*,WIDE2-1,qAR,KC2WBX-2:!4307.14NT07914.94W#PHG6460
20260209165455VE3PLF-1>APN383,VE3RSB,WIDE2*,qAR,KC2WBX-2:!4307.14NT07914.94W#PHG6460
20260209172856VE3PLF-1>APN383,VE3RSB*,WIDE2-1,qAO,VA3CQC-1:!4307.14NT07914.94W#PHG6460
20260209175455VE3PLF-1>APN383,VE3RSB,WIDE2*,qAR,KC2WBX-2:!4307.14NT07914.94W#PHG6460
20260209182925VE3PLF-1>APN383,VE3RSB*,WIDE2-1,qAR,KC2WBX-2:!4307.14NT07914.94W#PHG6460