APRS Packet Errors for KP4AP (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
20190422063409KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190422065051KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190422070737KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190422072425KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190422074127KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190422075813KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190422081518KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190422083210KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190422084907KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190422090605KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190422092257KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190422093954KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190422095647KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190422101400KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190422103102KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190422104806KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190422110458KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190422115618KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190422121318KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz