APRS Packet Errors for N3ZQY (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
20190420122304N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190420123956N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190420125634N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190420131314N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190420132956N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190420134647N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190420140325N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190420142009N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190420143653N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190420145347N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190420151027N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190420152705N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190420154346N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190420160036N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190420161721N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190420163413N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190420165054N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190420170740N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190420172417N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190420174053N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190420175731N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190420181416N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz