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
20260209130939N9CVR-10>APRX29,TCPIP*,qAC,T2CAEAST:!4411.15NT08832.30W&TX iGate de N9CVR
20260209133802N9CVR-10>APRX29,TCPIP*,qAC,T2CAEAST:!4411.15NT08832.30W&TX iGate de N9CVR
20260209140502N9CVR-10>APRX29,TCPIP*,qAC,T2CAEAST:!4411.15NT08832.30W&TX iGate de N9CVR
20260209143347N9CVR-10>APRX29,TCPIP*,qAC,T2CAEAST:!4411.15NT08832.30W&TX iGate de N9CVR
20260209150235N9CVR-10>APRX29,TCPIP*,qAC,T2CAEAST:!4411.15NT08832.30W&TX iGate de N9CVR
20260209152853N9CVR-10>APRX29,TCPIP*,qAC,T2CAEAST:!4411.15NT08832.30W&TX iGate de N9CVR
20260209155741N9CVR-10>APRX29,qAo,ND9DW-11:!4411.15NT08832.30W&TX iGate de N9CVR
20260209162644N9CVR-10>APRX29,TCPIP*,qAC,T2CAEAST:!4411.15NT08832.30W&TX iGate de N9CVR
20260209165254N9CVR-10>APRX29,TCPIP*,qAC,T2CAEAST:!4411.15NT08832.30W&TX iGate de N9CVR
20260209172119N9CVR-10>APRX29,TCPIP*,qAC,T2CAEAST:!4411.15NT08832.30W&TX iGate de N9CVR
20260209175004N9CVR-10>APRX29,TCPIP*,qAC,T2CAEAST:!4411.15NT08832.30W&TX iGate de N9CVR
20260209181544N9CVR-10>APRX29,TCPIP*,qAC,T2CAEAST:!4411.15NT08832.30W&TX iGate de N9CVR
20260209184319N9CVR-10>APRX29,TCPIP*,qAC,T2CAEAST:!4411.15NT08832.30W&TX iGate de N9CVR