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
20190825115840N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190825121537N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190825123255N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190825125001N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190825130700N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190825132402N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190825134111N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190825135814N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190825141516N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190825143221N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190825144939N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190825150646N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190825152357N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190825154057N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190825155819N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190825161532N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190825163231N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190825164934N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190825170645N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190825172357N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz
20190825174108N3ZQY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)N3ZQY-DP!4029.20N/-78-25.22rRNG0034 IPSC2-BRAZIL MMDVM 441.6000@+5.0 MHz