APRS Packet Errors for DB0BH (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
20260208143926DB0BH>APGE01,TCPIP*,qAC,T2FMNETZ:!4926.10N/01018.74ErDB0BH Echolink Node Nummer 457767
20260208153925DB0BH>APGE01,TCPIP*,qAC,T2FMNETZ:!4926.10N/01018.74ErDB0BH Simplex-Link 430.025MHz CTCSS 79,7Hz
20260208155425DB0BH>APGE01,TCPIP*,qAC,T2FMNETZ:!4926.10N/01018.74ErDB0BH Echolink Node Nummer 457767
20260208165425DB0BH>APGE01,TCPIP*,qAC,T2FMNETZ:!4926.10N/01018.74ErDB0BH Simplex-Link 430.025MHz CTCSS 79,7Hz
20260208170925DB0BH>APGE01,TCPIP*,qAC,T2FMNETZ:!4926.10N/01018.74ErDB0BH Echolink Node Nummer 457767
20260208180925DB0BH>APGE01,TCPIP*,qAC,T2FMNETZ:!4926.10N/01018.74ErDB0BH Simplex-Link 430.025MHz CTCSS 79,7Hz
20260208182425DB0BH>APGE01,TCPIP*,qAC,T2FMNETZ:!4926.10N/01018.74ErDB0BH Echolink Node Nummer 457767
20260208192425DB0BH>APGE01,TCPIP*,qAC,T2FMNETZ:!4926.10N/01018.74ErDB0BH Simplex-Link 430.025MHz CTCSS 79,7Hz
20260208193925DB0BH>APGE01,TCPIP*,qAC,T2FMNETZ:!4926.10N/01018.74ErDB0BH Echolink Node Nummer 457767