APRS Packet Errors for DMREA4 (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
20190616085549DMREA4>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA4-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7000 MHz
20190616091244DMREA4>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA4-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7000 MHz
20190616092936DMREA4>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA4-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7000 MHz
20190616094629DMREA4>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA4-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7000 MHz
20190616100326DMREA4>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA4-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7000 MHz
20190616102015DMREA4>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA4-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7000 MHz
20190616103718DMREA4>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA4-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7000 MHz
20190616105423DMREA4>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA4-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7000 MHz
20190616111127DMREA4>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA4-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7000 MHz
20190616112827DMREA4>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA4-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7000 MHz
20190616114522DMREA4>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA4-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7000 MHz
20190616120219DMREA4>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA4-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7000 MHz
20190616121921DMREA4>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA4-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7000 MHz
20190616123629DMREA4>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA4-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7000 MHz
20190616125327DMREA4>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA4-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7000 MHz
20190616131022DMREA4>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA4-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7000 MHz
20190616132722DMREA4>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA4-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7000 MHz
20190616134424DMREA4>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA4-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7000 MHz
20190616140120DMREA4>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA4-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7000 MHz
20190616141819DMREA4>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA4-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7000 MHz
20190616143520DMREA4>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA4-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.7000 MHz