This week
Chris is hosting MIN. We project 84.9 receiving yards on 9.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
Chris has averaged 84% of his team's snaps across 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. Opportunity is the first thing the model reads and the last thing it gives up on — production without snaps is noise, and snaps without production usually corrects.
What kind of receiver he is
Chris has caught 135 of 204 targets (66%) for 1654 yards and 10 touchdowns — 8.1 yards per target. Yards per target is the honest efficiency number here, because catch rate mostly measures how far downfield he's used: a slot receiver on screens will always catch more of them than a deep threat, without being better.
His last 5 games
Over that stretch Chris has 610 total yards. In a sport with seventeen games, a five-game window is closer to an anecdote than a trend — which is why usage, not this, anchors the number.
How the model reads him
The number on Chris is a share of a simulated game. First the matchup: possessions, field position, how each offense is likely to move. Then his slice of it, set by usage rather than by reputation. How those pieces are weighted is ours and gets re-tuned against results; the output is published and graded, which is the half you can check.
What we'd flag
Football's sample sizes are brutal — seventeen games a season means a "trend" is often four data points. Injuries and game script move usage more than talent does week to week, and a blowout can erase a starter's second half.