Last scored matchup
Luis isn't on today's slate. He was last scored yesterday, at home against Tampa Bay Rays on Wednesday, October 7, 2026, where he landed on hits (92/100), doubles (77.4/100), h+r+rbi (70.3/100). This page refreshes with new projections as soon as he's back in a lineup.
He's in a cold stretch
Luis is 7-for-34 (.206) across his last 10 games, down from .285 on the season. Slumps this size are mostly noise at this sample — 34 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
Luis has 30 home runs and 59 extra-base hits in 474 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
Luis 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
Luis has recorded at least one hit in 81 of 132 games he's batted in — 61% — with 37 multi-hit games among them. That's about average — most regulars land somewhere near it.
Home and away
Luis is hitting .301 at home (77-for-256) and .266 on the road (58-for-218) 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 Tampa Bay Rays
Luis is 2-for-21 (.095) against Tampa Bay Rays in our log, over 6 games. Worth knowing, worth not over-reading. 21 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
Luis's biggest night was Wednesday, September 30, 2026 against BOS — 3-for-5 with 1 homer, 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 Luis have graded
We've ranked Luis a top-20 hitter matchup 43 times this season. He got a hit in 29 of them — 67%. 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
Luis was scored on 12 boards in that matchup, and the spread is the interesting part: hits graded 92/100 while walks came in at 17.3/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
Luis 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.