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
20260314142834VE1DC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE1DC-DP!4522200.00N/06308.rRNG0034 IPSC2-FreeSTAR MMDVM 433.7500 MHz
20260314145942VE1DC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE1DC-DP!4522200.00N/06308.rRNG0034 IPSC2-FreeSTAR MMDVM 433.7500 MHz
20260314153039VE1DC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE1DC-DP!4522200.00N/06308.rRNG0034 IPSC2-FreeSTAR MMDVM 433.7500 MHz
20260314160131VE1DC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE1DC-DP!4522200.00N/06308.rRNG0034 IPSC2-FreeSTAR MMDVM 433.7500 MHz
20260314163226VE1DC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE1DC-DP!4522200.00N/06308.rRNG0034 IPSC2-FreeSTAR MMDVM 433.7500 MHz
20260314170322VE1DC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE1DC-DP!4522200.00N/06308.rRNG0034 IPSC2-FreeSTAR MMDVM 433.7500 MHz
20260314173439VE1DC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE1DC-DP!4522200.00N/06308.rRNG0034 IPSC2-FreeSTAR MMDVM 433.7500 MHz
20260314180534VE1DC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE1DC-DP!4522200.00N/06308.rRNG0034 IPSC2-FreeSTAR MMDVM 433.7500 MHz
20260314183627VE1DC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE1DC-DP!4522200.00N/06308.rRNG0034 IPSC2-FreeSTAR MMDVM 433.7500 MHz
20260314190713VE1DC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE1DC-DP!4522200.00N/06308.rRNG0034 IPSC2-FreeSTAR MMDVM 433.7500 MHz