APRS Packet Errors for DMREA1 (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
20190818074056DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190818075744DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190818081438DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190818083137DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190818084836DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190818090524DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190818092219DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190818093912DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190818095603DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190818101253DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190818102946DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190818110900DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190818112554DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190818114248DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190818115940DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190818121632DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190818123323DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190818125012DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190818130702DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190818132356DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz