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
20181212231416VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20181212232949VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20181212234528VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20181213000106VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20181213001638VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20181213003213VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20181213004803VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20181213010335VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20181213011924VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20181213013501VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20181213015040VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20181213020614VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20181213022149VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20181213023726VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20181213025307VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20181213031118VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20181213032652VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20181213034232VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20181213035818VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20181213041353VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20181213042932VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20181213044507VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz
20181213050054VE2ZFP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE2ZFP-DP!4530.33N/-73-51.86rRNG0034 IPSC2-BRAZIL MMDVM 431.0300 MHz