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
20190222012042WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_049/010g t014r000p000P h80b10188KDvs
20190222015043WB7BKM-13>APK102,WALDEN,WIDE1,TABNSH,WIDE2*,qAR,SUNLGT:=09H6.00N/202E9.00p_023/010g t014r000p000P h82b10191KDvs
20190222025043WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_024/008g t014r000p000P h84b10194KDvs
20190222032044WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_022/010g t013r000p000P h84b10192KDvs
20190222042045WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_040/007g t013r000p000P h84b10199KDvs
20190222052045WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_017/004g t013r000p000P h84b10198KDvs
20190222055045WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_033/009g t013r000p000P h83b10196KDvs
20190222062046WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_010/007g t012r000p000P h82b10192KDvs
20190222065046WB7BKM-13>APK102,WALDEN,WIDE1*,WIDE2-1,qAR,SUNLGT:=09H6.00N/202E9.00p_348/005g t012r000p000P h81b10188KDvs