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
20191117214329VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191117215847VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191117221413VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191117222930VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191117224450VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191117230004VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191117231714VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191117233228VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191117234753VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191118000316VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191118001913VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191118003434VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191118004954VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191118010520VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191118012143VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191118013701VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191118015220VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191118020738VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191118022305VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191118023818VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191118025334VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191118030853VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191118032417VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191118033931VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz