APRS Packet Errors for KJ4LWZ (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
20190121101310KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190121102912KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190121104513KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190121110113KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190121111703KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190121113301KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190121114858KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190121120500KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190121122052KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190121123642KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190121125251KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190121130844KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190121132434KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190121134024KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190121135628KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190121141217KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190121142808KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190121144403KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190121145959KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190121151549KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190121153141KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190121154732KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190121160324KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz