If there is an outgoing transaction, then with the un/compressed public key and kangaroo or pollard, also possible.
Sadly this was an offline wallet, so it only ever had incoming transaction. It has never sent out.
So that would be very easy. ~60 missing bits, we would have the private key within minutes.
1 year ago, user PawGo calculated exactly your case (10 missing WIF characters) but
with the public key in less than 11 minutes.
Let's take WIF 5HrdZxkxnVst8Q_____keiLe1k4AmSDaAhqQVUYVxVSBkf5VfUu
Now, we may find the first WIF to be tested, it will be 5HrdZxkxnVst8Q11111keiLe1k4AmSDaAhqQVUYVxVSBkf5VfUu.
Not bad, no?

10 missing WIF characters - Less than 11 minutes on old CPU. GPU performance - to be seen.
That's fantastic. I'll have to go back to check Pollard's kangaroo algorithm again.
Thread: Using Kangaroo for WIF solving
http://bitcointalk.org/index.php?topic=5315607.0