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
20190217024237DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-RPTR MMDVM 143.9250 MHz
20190217025859DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-RPTR MMDVM 143.9250 MHz
20190217031516DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-RPTR MMDVM 143.9250 MHz
20190217033133DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-RPTR MMDVM 143.9250 MHz
20190217034750DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-RPTR MMDVM 143.9250 MHz
20190217040410DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-RPTR MMDVM 143.9250 MHz
20190217042028DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-RPTR MMDVM 143.9250 MHz
20190217043645DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-RPTR MMDVM 143.9250 MHz
20190217045302DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-RPTR MMDVM 143.9250 MHz
20190217050922DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-RPTR MMDVM 143.9250 MHz
20190217052539DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-RPTR MMDVM 143.9250 MHz
20190217054157DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-RPTR MMDVM 143.9250 MHz
20190217055814DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-RPTR MMDVM 143.9250 MHz
20190217061434DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-RPTR MMDVM 143.9250 MHz
20190217063051DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-RPTR MMDVM 143.9250 MHz
20190217064709DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-RPTR MMDVM 143.9250 MHz
20190217070326DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-RPTR MMDVM 143.9250 MHz
20190217071946DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-RPTR MMDVM 143.9250 MHz
20190217073602DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-RPTR MMDVM 143.9250 MHz
20190217075219DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-RPTR MMDVM 143.9250 MHz