APRS Packet Errors for DO3DO (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
20190116112445DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190116114201DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190116115912DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190116121648DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190116123417DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190116125147DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190116130919DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190116132620DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190116134433DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190116140155DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190116141942DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190116143712DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190116145504DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190116151250DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190116153119DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190116154923DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190116160638DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190116162436DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190116164205DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190116171541DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz