APRS Packet Errors for GB3DV (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
20251026222815GB3DV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GB3DV-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 439.7000@-9.0 MHz
20251026225837GB3DV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GB3DV-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 439.7000@-9.0 MHz
20251026232859GB3DV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GB3DV-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 439.7000@-9.0 MHz
20251026235920GB3DV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GB3DV-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 439.7000@-9.0 MHz
20251027002941GB3DV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GB3DV-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 439.7000@-9.0 MHz
20251027010002GB3DV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GB3DV-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 439.7000@-9.0 MHz
20251027013021GB3DV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GB3DV-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 439.7000@-9.0 MHz
20251027030121GB3DV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GB3DV-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 439.7000@-9.0 MHz
20251027040202GB3DV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)GB3DV-DP!0000.00N/00000.00ErRNG0034 IPSC2-DVSPh-A MMDVM 439.7000@-9.0 MHz