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
20190824204516DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190824210219DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190824211921DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190824213616DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190824215309DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190824221006DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190824222709DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190824224405DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190824230057DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190824231752DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190824233447DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190824235143DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190825000834DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190825002524DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190825004215DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190825005911DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190825011603DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190825013255DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190825015005DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190825020711DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190825022359DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz
20190825024052DMREA1>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA1-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6250 MHz