APRS Packet Errors for VE3NDQ (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
20201204152339VE3NDQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3NDQ-DP!4300.00N/079-0.00WrRNG0034 IPSC2-QUADNET MMDVM 444.1000 MHz
20201204155440VE3NDQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3NDQ-DP!4300.00N/079-0.00WrRNG0034 IPSC2-QUADNET MMDVM 444.1000 MHz
20201204165636VE3NDQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3NDQ-DP!4300.00N/079-0.00WrRNG0034 IPSC2-QUADNET MMDVM 444.1000 MHz
20201204172726VE3NDQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3NDQ-DP!4300.00N/079-0.00WrRNG0034 IPSC2-QUADNET MMDVM 444.1000 MHz
20201204175824VE3NDQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3NDQ-DP!4300.00N/079-0.00WrRNG0034 IPSC2-QUADNET MMDVM 444.1000 MHz
20201204185959VE3NDQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3NDQ-DP!4300.00N/079-0.00WrRNG0034 IPSC2-QUADNET MMDVM 444.1000 MHz
20201204193050VE3NDQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3NDQ-DP!4300.00N/079-0.00WrRNG0034 IPSC2-QUADNET MMDVM 444.1000 MHz
20201204200127VE3NDQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3NDQ-DP!4300.00N/079-0.00WrRNG0034 IPSC2-QUADNET MMDVM 444.1000 MHz
20201204203219VE3NDQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3NDQ-DP!4300.00N/079-0.00WrRNG0034 IPSC2-QUADNET MMDVM 444.1000 MHz