APRS Packet Errors for N5CBP-6 (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
20260209120242N5CBP-6>APRS,TCPIP*,qAC,T2TEXAS:@120241h3007.97N8242.47Wa,/W2147.180MHz TOFF - iGate
20260209123242N5CBP-6>APRS,TCPIP*,qAC,T2TEXAS:@123241h3007.97N8242.47Wa,/W2147.180MHz TOFF - iGate
20260209130242N5CBP-6>APRS,TCPIP*,qAC,T2TEXAS:@130241h3007.97N8242.47Wa,/W2147.180MHz TOFF - iGate
20260209133242N5CBP-6>APRS,TCPIP*,qAC,T2TEXAS:@133241h3007.97N8242.47Wa,/W2147.180MHz TOFF - iGate
20260209140242N5CBP-6>APRS,TCPIP*,qAC,T2TEXAS:@140241h3007.97N8242.47Wa,/W2147.180MHz TOFF - iGate
20260209143242N5CBP-6>APRS,TCPIP*,qAC,T2TEXAS:@143241h3007.97N8242.47Wa,/W2147.180MHz TOFF - iGate
20260209150242N5CBP-6>APRS,TCPIP*,qAC,T2TEXAS:@150241h3007.97N8242.47Wa,/W2147.180MHz TOFF - iGate
20260209153242N5CBP-6>APRS,TCPIP*,qAC,T2TEXAS:@153241h3007.97N8242.47Wa,/W2147.180MHz TOFF - iGate
20260209160242N5CBP-6>APRS,TCPIP*,qAC,T2TEXAS:@160241h3007.97N8242.47Wa,/W2147.180MHz TOFF - iGate
20260209163242N5CBP-6>APRS,TCPIP*,qAC,T2TEXAS:@163241h3007.97N8242.47Wa,/W2147.180MHz TOFF - iGate
20260209170242N5CBP-6>APRS,TCPIP*,qAC,T2TEXAS:@170241h3007.97N8242.47Wa,/W2147.180MHz TOFF - iGate
20260209173242N5CBP-6>APRS,TCPIP*,qAC,T2TEXAS:@173241h3007.97N8242.47Wa,/W2147.180MHz TOFF - iGate