APRS Packet Errors for WB7BKM-13 (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
20170428234330WB7BKM-13>APK102,WB7GR-4*,WIDE2-1,qAR,WB7GR-10:=0000.00N/00000.00W_057/012g t026r000p000P h90b10133KDvs
20170429001331WB7BKM-13>APK102,WB7GR-3,WB7GR-2*,qAR,WB7GR-10:=0000.00N/00000.00W_068/005g t025r000p000P h91b10145KDvs
20170429021331WB7BKM-13>APK102,WB7GR-4*,WIDE2-1,qAR,WB7GR-10:=0000.00N/00000.00W_019/011g t022r000p000P h91b10179KDvs
20170429024332WB7BKM-13>APK102,WB7GR-3*,WIDE2-1,qAR,WB7GR-10:=0000.00N/00000.00W_057/005g t022r000p000P h90b10191KDvs
20170429031332WB7BKM-13>APK102,WB7GR-3*,WIDE2-1,qAR,WB7GR-10:=0000.00N/00000.00W_071/004g t022r000p000P h90b10198KDvs
20170429041334WB7BKM-13>APK102,WB7GR-3*,WIDE2-1,qAR,WB7GR-10:=0000.00N/00000.00W_068/004g t022r000p000P h90b10208KDvs
20170429044334WB7BKM-13>APK102,WB7GR-3*,WIDE2-1,qAR,WB7GR-10:=0000.00N/00000.00W_098/007g t021r000p000P h90b10209KDvs
20170429051334WB7BKM-13>APK102,WB7GR-3*,WIDE2-1,qAR,WB7GR-10:=0000.00N/00000.00W_075/001g t021r000p000P h90b10213KDvs