This week
Luther is on the road against CAR. We project 39.5 receiving yards on 4.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
Luther has averaged 42% of his team's snaps across 17 games. That's a limited role, and it caps everything else on this page. A player on a third of the snaps can't produce like a starter no matter how efficient he is, and the projection reflects the opportunity rather than the talent. 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
Luther has caught 53 of 74 targets (72%) for 718 yards and 2 touchdowns — 9.7 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 Luther has 329 total yards. Worth noting: his snap share is trending up — 55% lately against 42% overall. 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 Luther 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.