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
20190422142832EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190422144519EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190422150215EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190422151915EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190422153603EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190422155257EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190422160949EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190422162640EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190422164341EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190422170043EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190422171752EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190422173443EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190422175156EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190422180900EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190422182621EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190422184313EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190422190030EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190422191731EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190422193439EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190422195126EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190422200819EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz