APRS Packet Errors for MB6BK (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
20190615215043MB6BK>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)MB6BK-DP!5125.20N/000-44.10rRNG0034 IPSC2-PhoenixF MMDVM 144.8500 MHz
20190615220810MB6BK>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)MB6BK-DP!5125.20N/000-44.10rRNG0034 IPSC2-PhoenixF MMDVM 144.8500 MHz
20190615222508MB6BK>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)MB6BK-DP!5125.20N/000-44.10rRNG0034 IPSC2-PhoenixF MMDVM 144.8500 MHz
20190615224214MB6BK>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)MB6BK-DP!5125.20N/000-44.10rRNG0034 IPSC2-PhoenixF MMDVM 144.8500 MHz
20190615225925MB6BK>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)MB6BK-DP!5125.20N/000-44.10rRNG0034 IPSC2-PhoenixF MMDVM 144.8500 MHz
20190615231626MB6BK>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)MB6BK-DP!5125.20N/000-44.10rRNG0034 IPSC2-PhoenixF MMDVM 144.8500 MHz
20190615233332MB6BK>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)MB6BK-DP!5125.20N/000-44.10rRNG0034 IPSC2-PhoenixF MMDVM 144.8500 MHz
20190615235029MB6BK>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)MB6BK-DP!5125.20N/000-44.10rRNG0034 IPSC2-PhoenixF MMDVM 144.8500 MHz
20190616000750MB6BK>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)MB6BK-DP!5125.20N/000-44.10rRNG0034 IPSC2-PhoenixF MMDVM 144.8500 MHz
20190616002509MB6BK>APZDMR,QTH,TCPIP*,qAU,T2IRELAND:)MB6BK-DP!5125.20N/000-44.10rRNG0034 IPSC2-PhoenixF MMDVM 144.8500 MHz