APRS Packet Errors for DL2OBX (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
20190325203955DL2OBX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL2OBX-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.3500@-4.0 MHz
20190325205722DL2OBX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL2OBX-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.3500@-4.0 MHz
20190325211445DL2OBX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL2OBX-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.3500@-4.0 MHz
20190325213218DL2OBX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL2OBX-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.3500@-4.0 MHz
20190325215000DL2OBX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL2OBX-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.3500@-4.0 MHz
20190325220756DL2OBX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL2OBX-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.3500@-4.0 MHz
20190325222514DL2OBX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL2OBX-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.3500@-4.0 MHz
20190325224224DL2OBX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DL2OBX-DP!5000.00N/-0300.00ErRNG0034 IPSC2-DL-HOTSPOT MMDVM 434.3500@-4.0 MHz