APRS Packet Errors for VE1DC (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
20240502230523VE1DC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE1DC-DP!5000.00N/003-0.00WrRNG0034 IPSC2-FreeSTAR MMDVM 433.6500 MHz
20240502233610VE1DC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE1DC-DP!5000.00N/003-0.00WrRNG0034 IPSC2-FreeSTAR MMDVM 433.6500 MHz
20240503000657VE1DC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE1DC-DP!5000.00N/003-0.00WrRNG0034 IPSC2-FreeSTAR MMDVM 433.6500 MHz
20240503003746VE1DC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE1DC-DP!5000.00N/003-0.00WrRNG0034 IPSC2-FreeSTAR MMDVM 433.6500 MHz
20240503010840VE1DC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE1DC-DP!5000.00N/003-0.00WrRNG0034 IPSC2-FreeSTAR MMDVM 433.6500 MHz
20240503013923VE1DC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE1DC-DP!5000.00N/003-0.00WrRNG0034 IPSC2-FreeSTAR MMDVM 433.6500 MHz
20240503021008VE1DC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE1DC-DP!5000.00N/003-0.00WrRNG0034 IPSC2-FreeSTAR MMDVM 433.6500 MHz
20240503024052VE1DC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE1DC-DP!5000.00N/003-0.00WrRNG0034 IPSC2-FreeSTAR MMDVM 433.6500 MHz