APRS Packet Errors for N9CVR-10 (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
20260208145726N9CVR-10>APRX29,TCPIP*,qAC,T2RDU:!4411.15NT08832.30W&TX iGate de N9CVR
20260208152609N9CVR-10>APRX29,TCPIP*,qAC,T2RDU:!4411.15NT08832.30W&TX iGate de N9CVR
20260208155353N9CVR-10>APRX29,TCPIP*,qAC,T2RDU:!4411.15NT08832.30W&TX iGate de N9CVR
20260208162145N9CVR-10>APRX29,TCPIP*,qAC,T2RDU:!4411.15NT08832.30W&TX iGate de N9CVR
20260208164915N9CVR-10>APRX29,TCPIP*,qAC,T2RDU:!4411.15NT08832.30W&TX iGate de N9CVR
20260208171522N9CVR-10>APRX29,TCPIP*,qAC,T2RDU:!4411.15NT08832.30W&TX iGate de N9CVR
20260208174009N9CVR-10>APRX29,TCPIP*,qAC,T2RDU:!4411.15NT08832.30W&TX iGate de N9CVR
20260208180822N9CVR-10>APRX29,TCPIP*,qAC,T2RDU:!4411.15NT08832.30W&TX iGate de N9CVR
20260208183649N9CVR-10>APRX29,TCPIP*,qAC,T2RDU:!4411.15NT08832.30W&TX iGate de N9CVR
20260208190449N9CVR-10>APRX29,TCPIP*,qAC,T2RDU:!4411.15NT08832.30W&TX iGate de N9CVR
20260208193314N9CVR-10>APRX29,TCPIP*,qAC,T2RDU:!4411.15NT08832.30W&TX iGate de N9CVR
20260208195759N9CVR-10>APRX29,TCPIP*,qAC,T2RDU:!4411.15NT08832.30W&TX iGate de N9CVR
20260208202402N9CVR-10>APRX29,TCPIP*,qAC,T2RDU:!4411.15NT08832.30W&TX iGate de N9CVR