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
20260208145500VE3PLF-1>APN383,VE3RSB,WIDE2*,qAO,VA3CQC-1:!4307.14NT07914.94W#PHG6460
20260208152801VE3PLF-1>APN383,VE3RSB*,WIDE2-1,qAO,VA3CQC-1:!4307.14NT07914.94W#PHG6460
20260208155500VE3PLF-1>APN383,VE3RSB,WIDE2*,qAO,VA3CQC-1:!4307.14NT07914.94W#PHG6460
20260208162833VE3PLF-1>APN383,VE3RSB*,WIDE2-1,qAO,VA3CQC-1:!4307.14NT07914.94W#PHG6460
20260208165500VE3PLF-1>APN383,VE3RSB,WIDE2*,qAR,KC2WBX-2:!4307.14NT07914.94W#PHG6460
20260208172901VE3PLF-1>APN383,VE3RSB*,WIDE2-1,qAR,KC2WBX-2:!4307.14NT07914.94W#PHG6460
20260208175519VE3PLF-1>APN383,VE3RSB,WIDE2*,qAR,KC2WBX-2:!4307.14NT07914.94W#PHG6460
20260208183000VE3PLF-1>APN383,VE3RSB*,WIDE2-1,qAR,KC2WBX-2:!4307.14NT07914.94W#PHG6460
20260208185518VE3PLF-1>APN383,VE3RSB,WIDE2*,qAR,KC2WBX-2:!4307.14NT07914.94W#PHG6460
20260208192959VE3PLF-1>APN383,VE3RSB*,WIDE2-1,qAR,KC2WBX-2:!4307.14NT07914.94W#PHG6460
20260208195500VE3PLF-1>APN383,VE3RSB,WIDE2*,qAO,VA3CQC-1:!4307.14NT07914.94W#PHG6460
20260208203030VE3PLF-1>APN383,VE3RSB*,WIDE2-1,qAR,KC2WBX-2:!4307.14NT07914.94W#PHG6460