APRS Packet Errors for EA5GVP (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
20190218162617EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190218164246EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190218165914EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190218171544EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190218173223EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190218174859EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190218180553EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190218182308EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190218184000EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190218185655EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190218191403EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190218193105EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190218194811EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190218200457EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190218202147EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190218203837EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190218205514EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190218211203EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190218212918EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190218214556EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190218220239EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz