Last scored matchup
Paul isn't on today's slate. He was last scored yesterday, at home against Toronto Blue Jays on Saturday, August 22, 2026, where he landed on h+r+rbi (58.6/100), total bases (58/100), hits (54.4/100). This page refreshes with new projections as soon as he's back in a lineup.
He's in a cold stretch
Paul is 3-for-20 (.150) across his last 10 games, down from .242 on the season. Slumps this size are mostly noise at this sample — 20 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.
What kind of hitter he is
Paul has 15 home runs and 26 extra-base hits in 285 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 right-handed bat
Paul 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
Paul has recorded at least one hit in 46 of 78 games he's batted in — 59% — with 21 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
Paul is hitting .210 at home (26-for-124) and .267 on the road (43-for-161) 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.
His best game in the log
Paul's biggest night was Wednesday, July 29, 2026 at CWS — 2-for-5 with 1 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 Paul have graded
We've ranked Paul a top-20 hitter matchup 26 times this season. He got a hit in 21 of them — 81%. 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
Paul was scored on 12 boards in that matchup, and the spread is the interesting part: h+r+rbi graded 58.6/100 while triples came in at 5.9/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
Paul 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.