Not on the current slate
Blake hasn't been scored in 54 days — his last matchup was against Cincinnati Reds on Tuesday, June 30, 2026. A gap that long usually means an injury, a minor-league option, or a roster move rather than a rest day. Everything below is his most recent real production, not a projection.
He bats from both sides
Blake is a switch-hitter, which changes how the model reads every one of his matchups. Most hitters carry a real platoon penalty — a lefty bat facing a good lefty arm is a materially worse spot, and the score drops accordingly. Blake takes the favourable side almost every night, so he doesn't collect that penalty. What moves his number instead is the quality of the arm rather than its handedness, and how the two sides of his own swing actually compare, which is rarely as balanced as the switch-hitter label suggests.
Floor and ceiling
Blake has recorded at least one hit in 11 of 34 games he's batted in — 32% — with 1 multi-hit game among them. That's a boom-or-bust profile. He'll carry a game outright and then go quiet for three, so his hits-board score tends to sit below hitters with worse power and better contact.
Home and away
Blake is hitting .143 at home (5-for-35) and .171 on the road (7-for-41) across the season. There's not much in it, which is the normal case. Home-road splits get talked about far more than they hold up.
Against Cincinnati Reds
Blake is 0-for-2 (.000) against Cincinnati Reds in our log, over 3 games. Worth knowing, worth not over-reading. 2 at-bats against one club is a tiny sample, and the model treats it as a minor input next to what that pitching staff actually allows to his handedness. Batter-versus-pitcher history is the most quoted number in baseball and one of the least predictive.
No graded record on him yet
We haven't ranked Blake a top-20 hitter matchup often enough this season to have a record worth publishing — not once so far. He's appeared in 48 graded games, so the log below is real; there just isn't a track record on our calls to show. It'll build here if the matchups start landing his way.
Where he lands across our boards
Blake was scored on 12 boards in that matchup, and the spread is the interesting part: stolen bases graded 40.4/100 while hits came in at 0.2/100. Same player, same game, same opposing arm — different questions. A spread that wide usually means the matchup favours one kind of outcome over another, and it's the clearest argument for reading the board that matches what you actually care about.
How the model reads him
Take the name off Blake and the model still produces the same number, because it's scoring the matchup rather than the player. His splits against this handedness, what the opposing starter and bullpen actually allow, how many plate appearances he's likely to get, the park, the weather, how he's swinging lately. All of it lands on a 0–100 scale against everyone else playing today. We don't publish how it's weighted. We publish every result it produces.
What we'd flag
Three caveats worth carrying. Not every player gets a posted line — book coverage runs to about 87% for confirmed starters, so a blank line is the market's silence, not ours. Lineup changes land late enough to strand a projection published hours earlier. And judging any of this on a single night is meaningless; the model is tuned on hundreds of settled outcomes. For Blake specifically, his sample is small (76 at-bats logged), and we don't have a meaningful graded record on him yet.