APRS Packet Errors for OK9DOB-8 (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
20260208152015OK9DOB-8>APRS,TCPIP*,qAC,T2CZECH:!4912.23N/01641.72E-Telemetry Sender v.037
20260208155018OK9DOB-8>APRS,TCPIP*,qAC,T2CZECH:!4912.23N/01641.72E-Telemetry Sender v.037
20260208162021OK9DOB-8>APRS,TCPIP*,qAC,T2PRT:!4912.23N/01641.72E-Telemetry Sender v.037
20260208165024OK9DOB-8>APRS,TCPIP*,qAC,T2PRT:!4912.23N/01641.72E-Telemetry Sender v.037
20260208172028OK9DOB-8>APRS,TCPIP*,qAC,T2SPAIN2:!4912.23N/01641.72E-Telemetry Sender v.037
20260208175030OK9DOB-8>APRS,TCPIP*,qAC,T2ROMANIA:!4912.23N/01641.72E-Telemetry Sender v.037
20260208182032OK9DOB-8>APRS,TCPIP*,qAC,T2POLC:!4912.23N/01641.72E-Telemetry Sender v.037
20260208185035OK9DOB-8>APRS,TCPIP*,qAC,T2CZECH:!4912.23N/01641.72E-Telemetry Sender v.037
20260208192038OK9DOB-8>APRS,TCPIP*,qAC,T2UK:!4912.23N/01641.72E-Telemetry Sender v.037
20260208195040OK9DOB-8>APRS,TCPIP*,qAC,T2ROMANIA:!4912.23N/01641.72E-Telemetry Sender v.037
20260208202043OK9DOB-8>APRS,TCPIP*,qAC,T2CSNGRAD:!4912.23N/01641.72E-Telemetry Sender v.037
20260208205048OK9DOB-8>APRS,TCPIP*,qAC,T2CSNGRAD:!4912.23N/01641.72E-Telemetry Sender v.037