APRS Packet Errors for DMREA5 (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
20190619200208DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190619201905DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190619203557DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190619205247DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190619210941DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190619212636DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190619214326DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190619220016DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190619221706DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190619223355DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190619225047DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190619230739DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190619232424DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190619234110DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190619235758DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190620001458DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190620003151DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190620004843DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190620010537DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190620012233DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190620013930DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz