Last scored matchup
Jordan isn't on today's slate. He was last scored 12 days ago, away at Milwaukee Brewers on Sunday, September 27, 2026, where he landed on singles (72.2/100), rbis (60.2/100), hits (59.4/100). This page refreshes with new projections as soon as he's back in a lineup.
He's in a cold stretch
Jordan is 4-for-37 (.108) across his last 10 games, down from .268 on the season. Slumps this size are mostly noise at this sample — 37 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
Jordan has 28 home runs and 61 extra-base hits in 604 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
Jordan 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
Jordan has recorded at least one hit in 108 of 157 games he's batted in — 69% — with 42 multi-hit games among them. That's about average — most regulars land somewhere near it.
Home and away
Jordan is hitting .271 at home (79-for-292) and .266 on the road (83-for-312) 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 Milwaukee Brewers
Jordan is 2-for-12 (.167) against Milwaukee Brewers in our log, over 3 games. Worth knowing, worth not over-reading. 12 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.
How our calls on Jordan have graded
We've ranked Jordan a top-20 hitter matchup 38 times this season. He got a hit in 28 of them — 74%. 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
Jordan was scored on 12 boards in that matchup, and the spread is the interesting part: singles graded 72.2/100 while triples came in at 4.1/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
Jordan 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.