APRS Packet Errors for VE2RTO-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
20260209092328VE2RTO-3>APDW18,TCPIP*,qAC,T2ALBERTA:!4518.75NR07214.47W&PHG0060Mont Orford Rx-only iGate
20260209095328VE2RTO-3>APDW18,TCPIP*,qAC,T2ALBERTA:!4518.75NR07214.47W&PHG0060Mont Orford Rx-only iGate
20260209102328VE2RTO-3>APDW18,TCPIP*,qAC,T2ALBERTA:!4518.75NR07214.47W&PHG0060Mont Orford Rx-only iGate
20260209105328VE2RTO-3>APDW18,TCPIP*,qAC,T2ALBERTA:!4518.75NR07214.47W&PHG0060Mont Orford Rx-only iGate
20260209112328VE2RTO-3>APDW18,TCPIP*,qAC,T2ALBERTA:!4518.75NR07214.47W&PHG0060Mont Orford Rx-only iGate
20260209115328VE2RTO-3>APDW18,TCPIP*,qAC,T2ALBERTA:!4518.75NR07214.47W&PHG0060Mont Orford Rx-only iGate
20260209122328VE2RTO-3>APDW18,TCPIP*,qAC,T2ALBERTA:!4518.75NR07214.47W&PHG0060Mont Orford Rx-only iGate
20260209125328VE2RTO-3>APDW18,TCPIP*,qAC,T2ALBERTA:!4518.75NR07214.47W&PHG0060Mont Orford Rx-only iGate
20260209132328VE2RTO-3>APDW18,TCPIP*,qAC,T2ALBERTA:!4518.75NR07214.47W&PHG0060Mont Orford Rx-only iGate
20260209135328VE2RTO-3>APDW18,TCPIP*,qAC,T2ALBERTA:!4518.75NR07214.47W&PHG0060Mont Orford Rx-only iGate
20260209142328VE2RTO-3>APDW18,TCPIP*,qAC,T2ALBERTA:!4518.75NR07214.47W&PHG0060Mont Orford Rx-only iGate
20260209145328VE2RTO-3>APDW18,TCPIP*,qAC,T2ALBERTA:!4518.75NR07214.47W&PHG0060Mont Orford Rx-only iGate