APRS Packet Errors for SV6NOB (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
20260309130428SV6NOB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6NOB-DP!60000.00N/60000.00rRNG0034 IPSC2-Poland MMDVM 434.0510@-0.0 MHz
20260309133526SV6NOB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6NOB-DP!60000.00N/60000.00rRNG0034 IPSC2-Poland MMDVM 434.0510@-0.0 MHz
20260309140625SV6NOB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6NOB-DP!60000.00N/60000.00rRNG0034 IPSC2-Poland MMDVM 434.0510@-0.0 MHz
20260309143722SV6NOB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6NOB-DP!60000.00N/60000.00rRNG0034 IPSC2-Poland MMDVM 434.0510@-0.0 MHz
20260309150821SV6NOB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6NOB-DP!60000.00N/60000.00rRNG0034 IPSC2-Poland MMDVM 434.0510@-0.0 MHz
20260309153921SV6NOB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6NOB-DP!60000.00N/60000.00rRNG0034 IPSC2-Poland MMDVM 434.0510@-0.0 MHz
20260309171226SV6NOB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6NOB-DP!60000.00N/60000.00rRNG0034 IPSC2-Poland MMDVM 434.0510@-0.0 MHz
20260309181428SV6NOB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)SV6NOB-DP!60000.00N/60000.00rRNG0034 IPSC2-Poland MMDVM 434.0510@-0.0 MHz