Not on the current slate
John hasn't been scored in 19 days — his last matchup was against Pittsburgh Pirates on Sunday, September 27, 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's in a cold stretch
John is 2-for-31 (.065) across his last 10 games, down from .162 on the season. Slumps this size are mostly noise at this sample — 31 at-bats is a fortnight, not a trend — and the model treats it that way, discounting the cold run rather than writing him off. If the matchup underneath is good, he'll still grade well here. That's a feature, and sometimes it's wrong.
He's a right-handed bat
John hits from the right side, so the platoon math runs the other way from a lefty's. Right-handed bats face right-handed pitching most of the time, meaning his baseline is built against the harder side and a left-handed starter is the upgrade. That's why a righty's score can jump on a day nothing else about the matchup changed. The model weighs his rates against the specific handedness he's drawing rather than a blended season number, which is where a lot of the day-to-day movement in his score comes from.
Floor and ceiling
John has recorded at least one hit in 9 of 20 games he's batted in — 45% — with 2 multi-hit games 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
John is hitting .156 at home (5-for-32) and .167 on the road (6-for-36) 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.
No graded record on him yet
We haven't ranked John a top-20 hitter matchup often enough this season to have a record worth publishing — not once so far. He's appeared in 24 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
John was scored on 12 boards in that matchup, and the spread is the interesting part: stolen bases graded 44.5/100 while total bases came in at 0/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
John gets scored the same way a backup infielder does — same inputs, same scale, no thumb on it. What he's done against arms of this handedness, what this particular pitcher and bullpen give up, his likely plate appearances, the ballpark, the conditions, his recent form. The weighting behind those is ours and gets re-tuned weekly against what actually happened. The output is public and graded, which is the only claim worth making.
What we'd flag
Read this page knowing what it can't do. It can't show you a line no book posted — coverage peaks around 87% for confirmed starters. It can't see a lineup change that happens after the projection publishes. And it can't tell you anything useful from one game, because the model is only measurable across a season-sized sample. For John specifically, his sample is small (68 at-bats logged), and we don't have a meaningful graded record on him yet.