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
20190617130209DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190617131900DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190617133555DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190617135248DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190617140939DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190617142627DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190617144315DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190617150004DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190617151655DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190617155224DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190617160906DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190617162546DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190617164235DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190617165928DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190617171622DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190617173327DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190617175017DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190617180710DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190617182403DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz
20190617184055DMREA2>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)DMREA2-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA-Hotspot MMDVM 145.6500 MHz