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
20190615214425KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190615214558KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA1Master MMDVM 146.5700 MHz
20190615215302KP4AP>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-Mexico MMDVM 146.5700 MHz
20190615215522KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190615220108KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190615220237KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA1Master MMDVM 146.5700 MHz
20190615220947KP4AP>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-Mexico MMDVM 146.5700 MHz
20190615221212KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190615221751KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190615221914KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA1Master MMDVM 146.5700 MHz
20190615222640KP4AP>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-Mexico MMDVM 146.5700 MHz
20190615222902KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190615223439KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz
20190615223552KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA1Master MMDVM 146.5700 MHz
20190615224329KP4AP>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-Mexico MMDVM 146.5700 MHz
20190615224551KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190615225126KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA-Hotspot MMDVM 146.5700 MHz