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
20190124064541KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190124070130KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190124071722KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190124073312KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190124074901KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190124080456KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190124082051KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190124083647KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190124085248KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190124090838KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190124092438KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190124094044KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190124095651KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190124101242KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190124102838KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190124104432KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190124110033KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190124111627KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190124113241KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190124114850KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190124120449KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz
20190124122051KJ4LWZ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KJ4LWZ-DP!2717.54N/-80-22.60rRNG0034 IPSC2-EA1Master MMDVM 446.2500 MHz