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
20190626025319DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626031006DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626032655DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626034339DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626040024DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626041713DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626043404DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626045053DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626050742DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626052431DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626054120DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626055807DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626061454DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626063142DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626064830DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626070519DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626073858DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626075549DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626081234DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626082922DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz