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
20190221003527EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190221005153EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190221010824EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190221012453EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190221014121EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190221015748EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190221021418EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190221023047EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190221024715EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190221030345EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190221032014EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190221033644EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190221035312EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190221040941EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190221042610EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190221044240EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190221045907EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190221051533EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190221053204EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190221054831EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190221060503EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz
20190221062129EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/-03-55.59rRNG0034 IPSC2-EA4Master MMDVM 430.3950 MHz