APRS Packet Errors for DMREA2 (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
20190620135725DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190620141408DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190620143055DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190620144744DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190620150435DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190620152137DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190620153835DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190620155540DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190620161247DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190620162942DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190620164631DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190620170320DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190620172012DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190620173657DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190620175349DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190620181035DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190620182726DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190620184425DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190620190112DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190620191800DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190620193452DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190620195139DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz