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
20190117005742WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_191/011g t031r000p000P h70b10165KDvs
20190117015743WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_180/009g t031r000p000P h67b10176KDvs
20190117025743WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_229/011g t030r000p000P h68b10181KDvs
20190117032744WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_241/011g t030r000p000P h67b10186KDvs
20190117035745WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_217/008g t030r000p000P h66b10189KDvs
20190117042745WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_223/011g t030r000p000P h68b10191KDvs
20190117045745WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_184/009g t029r000p000P h69b10187KDvs
20190117052745WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_162/015g t030r000p000P h67b10191KDvs
20190117055747WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_232/015g t030r000p000P h66b10191KDvs
20190117062746WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_225/008g t030r000p000P h65b10195KDvs