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
20190217142000KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190217143632KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190217145308KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190217150947KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190217152622KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190217154254KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190217155925KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190217161605KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190217163237KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190217164908KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190217170541KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190217172219KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190217173859KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190217175529KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190217181208KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190217182848KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190217184521KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190217190204KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190217191837KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190217193514KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190217195159KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190217200844KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz