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
20190421164647KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190421170345KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190421172112KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190421173821KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190421175514KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190421181219KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190421182917KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190421184638KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190421195503KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190421201153KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190421202842KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190421204546KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190421210253KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190421212013KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190421213707KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190421215355KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190421221058KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz
20190421222753KP4AP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)KP4AP-DP!1830.49N/-69-57.34rRNG0034 IPSC2-EA4Master MMDVM 146.5700 MHz