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
20190825011603DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190825013255DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190825015005DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190825020711DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190825022359DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190825024052DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190825025741DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190825031435DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190825033127DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190825034817DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190825040508DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190825042204DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190825043855DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190825045546DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190825051235DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190825052928DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190825054617DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190825060309DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190825061959DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190825063652DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190825065353DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz