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
20190823133638DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190823135347DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190823141051DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190823142803DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190823144515DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190823150218DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190823151927DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190823153632DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190823155342DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190823161051DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190823162802DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190823164512DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190823170227DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190823171937DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190823173646DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190823175355DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190823181102DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190823182808DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190823184514DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190823190214DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190823191921DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz