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
20191014213120VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191014214635VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191014220151VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191014221707VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191014223233VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191014224751VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191014230310VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191014231834VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191014234710VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86WrRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191015000224VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191015001743VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191015003306VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191015004836VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191015010350VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191015011907VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191015013423VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191015014952VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191015020506VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191015022023VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191015023543VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191015025107VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191015030620VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20191015032138VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz