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
20170426201245WB7BKM-13>APK102,WB7GR-4*,WIDE2-1,qAR,WB7GR-10:=0000.00N/00000.00W_227/003g t041r000p004P h63b10091KDvs
20170426204245WB7BKM-13>APK102,WB7GR-4*,WIDE2-1,qAR,WB7GR-10:=0000.00N/00000.00W_237/005g t041r000p004P h62b10087KDvs
20170426211249WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAr,SUNLGT:=0000.00N/00000.00W_203/011g t042r000p004P h60b10084KDvs
20170426214249WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAr,SUNLGT:=0000.00N/00000.00W_234/003g t033r000p004P h82b10084KDvs
20170426221246WB7BKM-13>APK102,WB7GR-4*,WIDE2-1,qAR,WB7GR-10:=0000.00N/00000.00W_214/012g t038r000p005P h72b10075KDvs
20170426224246WB7BKM-13>APK102,WB7GR-3*,WIDE2-1,qAR,WB7GR-10:=0000.00N/00000.00W_173/003g t034r000p005P h83b10077KDvs
20170427001248WB7BKM-13>APK102,WB7GR-4*,WIDE2-1,qAR,WB7GR-10:=0000.00N/00000.00W_197/006g t039r000p006P h69b10068KDvs
20170427004248WB7BKM-13>APK102,WB7GR-3*,WIDE2-1,qAR,WB7GR-10:=0000.00N/00000.00W_300/005g t035r000p006P h81b10071KDvs