This week
Tre is on the road against NE. We project 47.7 receiving yards on 5.4 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
Across 20 games, Tre has been on the field for 89% of his team's snaps. 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. The model weighs this above efficiency for a simple reason: snap share predicts next week better than last week's yardage does.
What kind of receiver he is
Tre has caught 70 of 112 targets (63%) for 875 yards and 5 touchdowns — 7.8 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 Tre has 267 total yards. Worth noting: his snap share is trending down — 70% lately against 89% overall. Five games is a small sample in any sport and a tiny one in football, where a team plays seventeen times a year — so recent form informs the projection without overriding the usage underneath it.
How the model reads him
Every projection here is built the same way for Tre as for a starter on a contender — simulate the game, then apportion it by role. No manual adjustments, no gut calls on who's due. The weighting behind it is proprietary and re-tuned on real outcomes; everything it produces is public and graded against the box score.
What we'd flag
Three things to carry. The season is seventeen games, so most trends here are small samples wearing a confident number. Game script rewrites usage — a team trailing throws, a team ahead runs. And injury news lands after we publish.