APRS Packet Errors for VE2ZFP (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
20190216194921VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 146.4900 MHz
20190216200555VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 146.4900 MHz
20190216202232VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 146.4900 MHz
20190216203908VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 146.4900 MHz
20190216205601VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 146.4900 MHz
20190216211234VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 146.4900 MHz
20190216212857VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 146.4900 MHz
20190216214539VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 146.4900 MHz
20190216220226VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 146.4900 MHz
20190216221855VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 146.4900 MHz
20190216223515VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 146.4900 MHz
20190216225147VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 146.4900 MHz
20190216230816VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 146.4900 MHz
20190216232436VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 146.4900 MHz
20190216234056VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 146.4900 MHz
20190216235721VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 146.4900 MHz
20190217001350VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 146.4900 MHz
20190217003006VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 146.4900 MHz
20190217004646VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 146.4900 MHz
20190217010321VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 146.4900 MHz
20190217012000VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 146.4900 MHz
20190217013616VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 146.4900 MHz