APRS Packet Errors for KL7BK (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
20180419212842	KL7BK>GPS,qAR,KL7AA-10:! 1!6129.15/N/14942.19W# Kinik/Goosebay
20180419215843	KL7BK>GPS,qAR,KL7AA-10:! 1!6129.15/N/14942.19W# Kinik/Goosebay
20180419222843	KL7BK>GPS,qAR,KL7AA-10:! 1!6129.15/N/14942.19W# Kinik/Goosebay
20180419225843	KL7BK>GPS,qAR,KL7AA-10:! 1!6129.15/N/14942.19W# Kinik/Goosebay
20180419232843	KL7BK>GPS,qAR,KL7AA-10:! 1!6129.15/N/14942.19W# Kinik/Goosebay
20180419235843	KL7BK>GPS,qAR,KL7AA-10:! 1!6129.15/N/14942.19W# Kinik/Goosebay
20180420002843	KL7BK>GPS,qAR,KL7AA-10:! 1!6129.15/N/14942.19W# Kinik/Goosebay
20180420005844	KL7BK>GPS,qAR,KL7AA-10:! 1!6129.15/N/14942.19W# Kinik/Goosebay
20180420012843	KL7BK>GPS,qAR,KL7AA-10:! 1!6129.15/N/14942.19W# Kinik/Goosebay
20180420015843	KL7BK>GPS,qAR,KL7AA-10:! 1!6129.15/N/14942.19W# Kinik/Goosebay
20180420022843	KL7BK>GPS,qAR,KL7AA-10:! 1!6129.15/N/14942.19W# Kinik/Goosebay
20180420025843	KL7BK>GPS,qAR,KL7AA-10:! 1!6129.15/N/14942.19W# Kinik/Goosebay