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
20190626142317DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626144016DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626145702DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626151350DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626153037DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626154727DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626160418DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626162107DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626163756DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626165449DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626171145DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626172833DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626174530DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626180226DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626181925DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626183620DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626185317DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626191018DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626192709DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626194405DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626200057DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz
20190626201754DMREA5>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA5-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7250 MHz