APRS Packet Errors for DMREA1 (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
20190716071447DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190716073142DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190716074837DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190716080529DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190716082224DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190716083921DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190716085620DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190716091315DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190716093013DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190716094724DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190716100430DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190716102125DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190716103825DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190716105525DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190716111237DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190716112939DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190716114633DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190716120329DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190716122045DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190716123750DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190716125457DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz