APRS Packet Errors for EB3CES (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
20190116085930EB3CES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CES-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 430.0000 MHz
20190116091522EB3CES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CES-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 430.0000 MHz
20190116093111EB3CES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CES-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 430.0000 MHz
20190116094700EB3CES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CES-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 430.0000 MHz
20190116100252EB3CES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CES-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 430.0000 MHz
20190116101848EB3CES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CES-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 430.0000 MHz
20190116103445EB3CES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CES-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 430.0000 MHz
20190116105035EB3CES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CES-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 430.0000 MHz
20190116110632EB3CES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CES-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 430.0000 MHz
20190116112235EB3CES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CES-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 430.0000 MHz
20190116113833EB3CES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CES-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 430.0000 MHz
20190116115431EB3CES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CES-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 430.0000 MHz
20190116121036EB3CES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CES-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 430.0000 MHz
20190116122641EB3CES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CES-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 430.0000 MHz
20190116124234EB3CES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CES-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 430.0000 MHz
20190116125835EB3CES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CES-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 430.0000 MHz
20190116131425EB3CES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CES-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 430.0000 MHz
20190116133025EB3CES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CES-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 430.0000 MHz
20190116134620EB3CES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CES-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 430.0000 MHz
20190116140221EB3CES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CES-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 430.0000 MHz
20190116141818EB3CES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CES-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 430.0000 MHz
20190116143413EB3CES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB3CES-DP!5000.00N/-0300.00ErRNG0034 IPSC2-EA1Master MMDVM 430.0000 MHz