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
20190615230810DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190615232456DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190615234138DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190615235827DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190616001512DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190616003156DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190616004843DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190616010527DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190616012210DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190616013904DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190616015600DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190616021249DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190616022937DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190616024621DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190616030305DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190616031950DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190616033634DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190616035316DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190616040957DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190616042647DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190616044329DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz