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
20190222154559EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190222160302EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190222161949EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190222163634EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190222165326EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190222171020EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190222172717EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190222174355EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190222180036EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190222181736EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190222183424EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190222185119EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190222190814EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190222192527EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190222194225EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190222195924EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190222201609EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190222203254EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190222204944EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190222210639EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190222212325EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz