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
20171218083658WB7BKM-13>APK102,WB7GR-4*,WIDE2-1,qAR,WB7GR-10:=0000.00N/00000.00W_234/014g t025r000p000P h57b10228KDvs
20171218093659WB7BKM-13>APK102,WB7GR-4*,WIDE2-1,qAR,WB7GR-10:=0000.00N/00000.00W_257/010g t025r000p000P h59b10227KDvs
20171218100659WB7BKM-13>APK102,WB7GR-3*,WIDE2-1,qAR,W0UPS-10:=0000.00N/00000.00W_223/013g t025r000p000P h60b10222KDvs
20171218103701WB7BKM-13>APK102,WB7GR-3*,WIDE2-1,qAR,WB7GR-10:=0000.00N/00000.00W_267/016g t024r000p000P h61b10217KDvs
20171218110702WB7BKM-13>APK102,WB7GR-3*,WIDE2-1,qAR,WB7GR-10:=0000.00N/00000.00W_222/010g t023r000p000P h61b10217KDvs
20171218113703WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAr,SUNLGT:=0000.00N/00000.00W_240/014g t024r000p000P h63b10211KDvs
20171218123703WB7BKM-13>APK102,WB7GR-4*,WIDE2-1,qAR,WB7GR-10:=0000.00N/00000.00W_244/007g t026r000p000P h63b10210KDvs
20171218130703WB7BKM-13>APK102,WB7GR-3*,WIDE2-1,qAR,WB7GR-10:=0000.00N/00000.00W_238/016g t027r000p000P h62b10209KDvs
20171218133704WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAr,SUNLGT:=0000.00N/00000.00W_228/014g t026r000p000P h63b10213KDvs
20171218140704WB7BKM-13>APK102,WB7GR-4*,WIDE2-1,qAR,WB7GR-10:=0000.00N/00000.00W_277/017g t026r000p000P h63b10211KDvs