Today's matchup
Nathan draws Kansas City Royals on the road today. He shows up on 12 boards — total bases (42.6/100, #67), doubles (35.9/100, #57), walks (25/100, #96), singles (21.2/100, #88). We've got him at 1.5 on the total bases board. Open any board row for the full breakdown of what's driving it.
He's swinging a hot bat
Nathan is 12-for-35 (.343) over his last 10 games — well clear of his .272 season mark. Our model does lean on recent form, but it weights it against the matchup rather than chasing it: a hot bat facing a tough arm in a bad park still grades as a tough spot. Streaks like this one also end without warning, which is why the score moves on the matchup and not on the streak.
What kind of hitter he is
Nathan has 10 home runs and 22 extra-base hits in 331 at-bats this season. That profile is why he grades better on the total-bases and home-run boards than his batting average alone would suggest — those boards reward damage, not just contact. Park and weather matter more for a hitter like him too, and both feed the score.
He's a left-handed bat
Nathan hits from the left side, and that's the first thing the model looks at. Left-handed hitters see right-handed pitching most nights, which is the favourable side — so a lefty bat's baseline is set against righties, and drawing a left-handed starter is a genuine downgrade rather than a rounding error. When you see his score fall on a day he's still in the lineup, an opposing lefty is usually why. Handedness also shapes the park read: pull-side geometry matters more for a left-handed swing than the raw park factor suggests.
Floor and ceiling
Nathan has recorded at least one hit in 61 of 96 games he's batted in — 64% — with 24 multi-hit games among them. That's about average — most regulars land somewhere near it.
Home and away
Nathan is hitting .252 at home (38-for-151) and .289 on the road (52-for-180) 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 Kansas City Royals
Nathan is 4-for-10 (.400) against Kansas City Royals in our log, over 3 games. Worth knowing, worth not over-reading. 10 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.
His best game in the log
Nathan's biggest night was Saturday, August 22, 2026 at NYY — 2-for-3 with 1 homer, 2 driven in. That's the ceiling, not the expectation. The projection you'll see on a board is closer to his typical game than his best one, which is the whole point of projecting rather than remembering.
How our calls on Nathan have graded
We've ranked Nathan a top-20 hitter matchup 35 times this season. He got a hit in 23 of them — 66%. That's the model reading him well, and it's the number we'd point to if you asked why we keep ranking him. It's also a season-sized sample on one player, which is smaller than it sounds; don't extrapolate it into a promise about tonight.
Where he lands across our boards
Nathan was scored on 12 boards in that matchup, and the spread is the interesting part: total bases graded 42.6/100 while h+r+rbi came in at 4.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
Nathan 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.