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
20190124072229DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190124073905DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190124075540DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190124081236DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190124082908DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190124084635DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190124090354DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190124092106DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190124093857DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190124095648DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190124101348DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190124103140DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190124104841DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190124110533DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190124112257DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190124114017DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190124115722DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190124121505DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190124123306DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190124125043DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190124130954DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz