APRS Packet Errors for SV9OFV (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
20260313080824SV9OFV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV9OFV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 434.5125 MHz
20260313083859SV9OFV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV9OFV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 434.5125 MHz
20260313090943SV9OFV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV9OFV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 434.5125 MHz
20260313094028SV9OFV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV9OFV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 434.5125 MHz
20260313101105SV9OFV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV9OFV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 434.5125 MHz
20260313104131SV9OFV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV9OFV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 434.5125 MHz
20260313111158SV9OFV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV9OFV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 434.5125 MHz
20260313114235SV9OFV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV9OFV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 434.5125 MHz
20260313121302SV9OFV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV9OFV-DP!5000.00N/003-0.00WrRNG0034 IPSC2-GR-DMO MMDVM 434.5125 MHz