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
20190118064159DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190118065938DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190118071603DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190118073317DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190118075102DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190118080826DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190118082530DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190118084242DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190118090009DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190118091755DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190118093552DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190118095323DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190118101105DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190118102831DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190118104601DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190118110359DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190118112238DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190118114032DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190118115814DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz
20190118121549DO3DO>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DO3DO-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.6250 MHz