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
20190916153251DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190916154815DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190916160334DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190916161853DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190916163412DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190916164934DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190916170454DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190916172014DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190916173533DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190916175057DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190916180617DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190916182136DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190916183655DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190916185217DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190916190737DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190916192258DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190916193818DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190916195341DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190916200900DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190916202418DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190916203937DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190916205459DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190916211018DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz