APRS Packet Errors for VE3KMN (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
20190718095126VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190718100818VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190718102514VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190718104214VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190718105905VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190718111555VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190718113253VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190718114955VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190718120645VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190718122336VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190718124030VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190718125739VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190718131435VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190718133133VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190718134838VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190718140540VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190718142235VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190718143927VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190718145617VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190718151323VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190718153012VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190718154708VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz