APRS Packet Errors for SV1FMT (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
20250417065102SV1FMT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1FMT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 430.2000 MHz
20250417072157SV1FMT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1FMT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 430.2000 MHz
20250417082423SV1FMT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1FMT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 430.2000 MHz
20250417092635SV1FMT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1FMT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 430.2000 MHz
20250417095756SV1FMT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1FMT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 430.2000 MHz
20250417102907SV1FMT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1FMT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 430.2000 MHz
20250417110015SV1FMT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1FMT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 430.2000 MHz
20250417113125SV1FMT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1FMT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 430.2000 MHz
20250417120217SV1FMT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1FMT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 430.2000 MHz
20250417123316SV1FMT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV1FMT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO2 MMDVM 430.2000 MHz