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
20190220142015WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_210/010g t006r000p000P h68b10127KDvs
20190220145017WB7BKM-13>APK102,WALDEN,WIDE1,TABNSH,WIDE2*,qAR,SUNLGT:=09H6.00N/202E9.00p_240/011g t007r000p000P h68b10134KDvs
20190220162017WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_198/010g t011r000p000P h62b10142KDvs
20190220175017WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_243/018g t014r000p000P h47b10135KDvs
20190220182018WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_241/017g t015r000p000P h46b10137KDvs
20190220185019WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_214/014g t015r000p000P h50b10135KDvs
20190220192019WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_236/012g t015r000p000P h50b10135KDvs
20190220195020WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_242/013g t017r000p000P h45b10131KDvs