APRS Packet Errors for EA4AIV (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
20190420130158EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190420131853EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190420133554EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190420135254EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190420140951EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190420142650EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190420144358EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190420150051EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190420151742EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190420153441EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190420155148EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190420160856EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190420162603EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190420164311EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190420170004EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190420171656EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190420173404EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190420175121EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190420180845EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190420182601EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190420184333EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz