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
20190221174751EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190221180450EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190221182148EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190221183830EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190221185519EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190221191203EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190221192844EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190221194522EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190221200213EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190221201852EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190221203536EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190221205210EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190221210851EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190221212528EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190221214205EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190221215847EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190221221528EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190221223217EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190221224854EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190221230543EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz
20190221232234EA5GVP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GVP-DP!3855.93N/000-9.89ErRNG0034 IPSC2-EA4Master MMDVM 430.4000 MHz