No projection this week
Mike doesn't have a projection right now — either his team is on a bye, the week's slate hasn't been simulated yet, or he isn't in a position to draw usage. His game log and the usage read below are the real record either way, and this page picks him back up as soon as there's a game to simulate.
How much he's on the field
Mike has averaged 68% of his team's snaps across 20 games. That's a rotational-to-starter share. It's the number most likely to move his projection week to week, because a swing of ten points of snap share moves everything downstream with it. 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 defensive back he is
Mike has 86 tackles across 20 games — 4.3 a game. Add 1 sack. Tackle volume is a strange stat for a defensive back: the best coverage players sometimes post the fewest, because nothing is thrown their way. A rising tackle count can mean he's playing well in run support or that receivers are catching the ball in front of him, and the box score can't tell you which.
His last 5 games
Over that stretch Mike has 22 tackles. 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 Mike 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.