APRS Packet Errors for AB9DK (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
20190616005108AB9DK>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)AB9DK-DP!4427.88N/-87-58.56rRNG0034 IPSC2-MINNESOTA MMDVM 446.5000 MHz
20190616010759AB9DK>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)AB9DK-DP!4427.88N/-87-58.56rRNG0034 IPSC2-MINNESOTA MMDVM 446.5000 MHz
20190616012445AB9DK>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)AB9DK-DP!4427.88N/-87-58.56rRNG0034 IPSC2-MINNESOTA MMDVM 446.5000 MHz
20190616014128AB9DK>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)AB9DK-DP!4427.88N/-87-58.56rRNG0034 IPSC2-MINNESOTA MMDVM 446.5000 MHz
20190616021505AB9DK>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)AB9DK-DP!4427.88N/-87-58.56rRNG0034 IPSC2-MINNESOTA MMDVM 446.5000 MHz
20190616023156AB9DK>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)AB9DK-DP!4427.88N/-87-58.56rRNG0034 IPSC2-MINNESOTA MMDVM 446.5000 MHz
20190616024843AB9DK>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)AB9DK-DP!4427.88N/-87-58.56rRNG0034 IPSC2-MINNESOTA MMDVM 446.5000 MHz
20190616033904AB9DK>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)AB9DK-DP!4427.88N/-87-58.56rRNG0034 IPSC2-MINNESOTA MMDVM 446.5000 MHz
20190616035551AB9DK>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)AB9DK-DP!4427.88N/-87-58.56rRNG0034 IPSC2-MINNESOTA MMDVM 446.5000 MHz
20190616062630AB9DK>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)AB9DK-DP!4427.88N/-87-58.56rRNG0034 IPSC2-MINNESOTA MMDVM 446.5000 MHz