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
20190217141708VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20190217143347VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20190217145021VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20190217150702VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20190217152349VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20190217154030VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20190217155713VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20190217161345VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20190217163031VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20190217164712VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20190217170344VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20190217172026VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20190217173702VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20190217175348VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20190217181042VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20190217182735VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20190217184411VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20190217190053VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20190217191741VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20190217193425VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20190217195109VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20190217200819VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz