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
20190220011046DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190220012749DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190220014450DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190220020156DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190220021922DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190220023731DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190220025542DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190220031307DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190220032956DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190220034637DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190220040330DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190220042041DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190220043740DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190220045445DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190220051155DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190220052854DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190220054709DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190220060417DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190220062140DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190220063844DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz