This week
Jonathan is hosting BAL. We project 73.8 rushing yards, 21.2 receiving yards on 3.3 targets. The number comes out of a drive-level simulation of the game rather than a season average — it asks how many possessions his side is likely to get, what they do with them, and how much of that flows through him.
How much he's on the field
82% — that's Jonathan's average snap share over 20 games. That's a full-time role. Snap share at this level is the most stable input we have — it changes slowly, and it survives a bad game in a way that yardage never does. This is the number to check first on any football page. Everything else here is downstream of it.
What kind of back he is
Jonathan has 418 carries for 2105 yards (5 a carry) and 24 rushing touchdowns. He's also seen 61 targets for 392 yards — pass-game work is what separates a back who plays on third down from one who leaves the field, and it's worth more to a projection than the same yardage on the ground. Running-back yardage swings hard on the blocking in front of him, which is why the model weighs opportunity — carries and targets — above efficiency.
His last 5 games
Over that stretch Jonathan has 377 total yards. A handful of games is thin evidence in a seventeen-game season. It nudges the projection; it doesn't drive it.
How the model reads him
Jonathan's projection starts with the game, not with him. We simulate the matchup drive by drive — how many possessions each side gets, how far they travel, how often they score — and then ask what share of that flows through him given his role. That ordering matters: a productive player on a team that runs 55 plays a game has a lower ceiling than a lesser one on a team that runs 70.
What we'd flag
Read this knowing the limits. A seventeen-game season makes every rate noisy; game script can invert a player's usage inside one afternoon; and depth-chart changes often surface too late to be in the projection.