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
20190720073927VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190720075621VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190720081325VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190720083016VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190720084706VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190720090359VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190720092058VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190720093756VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190720095448VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190720101140VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190720102843VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190720104535VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190720110227VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190720111927VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190720113631VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190720121029VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190720122721VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190720124425VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190720130119VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz
20190720131812VE3KMN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VE3KMN-DP!4524.75N/-75-41.83rRNG0034 IPSC2-BRAZIL MMDVM 441.0250 MHz