APRS Packet Errors for R1BPV-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
20260208134526R1BPV-10>APDW16,TCPIP*,qAC,T2TROITSK:!6013.88NR03035.24E&144.800MHz 1200bps RX only IGate
20260208141447R1BPV-10>APDW16,TCPIP*,qAC,T2TROITSK:!6013.88NR03035.24E&144.800MHz 1200bps RX only IGate
20260208144557R1BPV-10>APDW16,TCPIP*,qAC,T2TROITSK:!6013.88NR03035.24E&144.800MHz 1200bps RX only IGate
20260208151447R1BPV-10>APDW16,TCPIP*,qAC,T2TROITSK:!6013.88NR03035.24E&144.800MHz 1200bps RX only IGate
20260208154447R1BPV-10>APDW16,TCPIP*,qAC,T2TROITSK:!6013.88NR03035.24E&144.800MHz 1200bps RX only IGate
20260208161447R1BPV-10>APDW16,TCPIP*,qAC,T2TROITSK:!6013.88NR03035.24E&144.800MHz 1200bps RX only IGate
20260208164446R1BPV-10>APDW16,TCPIP*,qAC,T2TROITSK:!6013.88NR03035.24E&144.800MHz 1200bps RX only IGate
20260208171446R1BPV-10>APDW16,TCPIP*,qAC,T2TROITSK:!6013.88NR03035.24E&144.800MHz 1200bps RX only IGate
20260208174446R1BPV-10>APDW16,TCPIP*,qAC,T2TROITSK:!6013.88NR03035.24E&144.800MHz 1200bps RX only IGate
20260208181446R1BPV-10>APDW16,TCPIP*,qAC,T2TROITSK:!6013.88NR03035.24E&144.800MHz 1200bps RX only IGate
20260208184446R1BPV-10>APDW16,TCPIP*,qAC,T2TROITSK:!6013.88NR03035.24E&144.800MHz 1200bps RX only IGate
20260208191446R1BPV-10>APDW16,TCPIP*,qAC,T2TROITSK:!6013.88NR03035.24E&144.800MHz 1200bps RX only IGate