APRS Packet Errors for VE2RQM-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
20260209133114	VE2RQM-3>APET10,WIDE2-2,qAR,VA2RVA-10:!4524.68N/07154.90Wr/V=0.0V ExpressTracker OP VA2HF
20260209140112	VE2RQM-3>APET10,WIDE2-2,qAO,VE2RTO-3:!4524.68N/07154.90Wr/V=0.0V ExpressTracker OP VA2HF
20260209143111	VE2RQM-3>APET10,WIDE2-2,qAR,VA2RVA-10:!4524.68N/07154.90Wr/V=0.0V ExpressTracker OP VA2HF
20260209150109	VE2RQM-3>APET10,WIDE2-2,qAO,VE2RTO-3:!4524.68N/07154.90Wr/V=0.0V ExpressTracker OP VA2HF
20260209153108	VE2RQM-3>APET10,WIDE2-2,qAO,VE2RTO-3:!4524.68N/07154.90Wr/V=0.0V ExpressTracker OP VA2HF
20260209160106	VE2RQM-3>APET10,WIDE2-2,qAO,VE2RTO-3:!4524.68N/07154.90Wr/V=0.0V ExpressTracker OP VA2HF
20260209163105	VE2RQM-3>APET10,WIDE2-2,qAR,VA2RVA-10:!4524.68N/07154.90Wr/V=0.0V ExpressTracker OP VA2HF
20260209170103	VE2RQM-3>APET10,WIDE2-2,qAR,VA2RVA-10:!4524.68N/07154.90Wr/V=0.0V ExpressTracker OP VA2HF
20260209173102	VE2RQM-3>APET10,WIDE2-2,qAR,VA2RVA-10:!4524.68N/07154.90Wr/V=0.0V ExpressTracker OP VA2HF
20260209180100	VE2RQM-3>APET10,WIDE2-2,qAO,VE2RTO-3:!4524.68N/07154.90Wr/V=0.0V ExpressTracker OP VA2HF
20260209183059	VE2RQM-3>APET10,WIDE2-2,qAO,VE2RTO-3:!4524.68N/07154.90Wr/V=0.0V ExpressTracker OP VA2HF
20260209190057	VE2RQM-3>APET10,WIDE2-2,qAR,VA2RVA-10:!4524.68N/07154.90Wr/V=0.0V ExpressTracker OP VA2HF