Not on the current slate
Pavin hasn't been scored in 31 days — his last matchup was against St. Louis Cardinals on Thursday, July 23, 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.
Recent form
Pavin is 3-for-32 (.094) over his last 10 games, in line with his .125 season line. No hot streak to fade, no slump to buy — the matchup is doing the work in his score, which is the normal case. The full game log is below.
He's a left-handed bat
Pavin 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
Pavin has recorded at least one hit in 7 of 23 games he's batted in — 30% — 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
Pavin is hitting .206 at home (7-for-34) and .053 on the road (2-for-38) across the season. That's a real-looking split, and it's the kind of thing that's usually part park and part noise. The model doesn't apply a blanket home-road adjustment — it prices the actual ballpark he's standing in, which is the part that carries signal.
No graded record on him yet
We haven't ranked Pavin a top-20 hitter matchup often enough this season to have a record worth publishing — 1 time 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
Pavin was scored on 12 boards in that matchup, and the spread is the interesting part: rbis graded 51.7/100 while runs came in at 18.7/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
Pavin 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 Pavin specifically, his sample is small (72 at-bats logged), and we don't have a meaningful graded record on him yet.