Rest-of-Season Rankings Week 5 Rankings Start/Sit Heat Index Defense vs Position Snap Counts Routes Run Player Props DFS Optimizer Defense Rankings Full Season Projections Best Ball Dynasty Stats

NFL Routes Run, YPRR and Target Share

2026 season
What each column means
Routes
Total routes run
Route %
% of his team's pass plays he ran a route
TPRR
Targets per route run
YPRR
Yards per route run
Tgt share
% of team's targets
Min route %
Filter. Hides anyone below that Route %. Not snaps.
Week
Position
Team Min route %
Player Team Pos Routes Route % Targets TPRR YPRR ADOT Tgt share Rec Yards
Rows
Page 1 of 1

Route stats, explained

What is yards per route run (YPRR)?

Receiving yards divided by the routes a player ran. It measures what he does with his chances rather than how many he gets, which is why it separates a good receiver on a run-heavy team from a genuinely inefficient one.

Above 2.00 is a strong week. The best receivers in the league live around 2.50 and up, and anything past 3.00 usually means a long touchdown is doing the work.

What is targets per route run (TPRR)?

How often a receiver gets thrown to when he runs a route. It strips out both team pass volume and the snaps he spent blocking, so it is the closest thing to a direct read on whether the quarterback is looking for him.

Above 25% is a focal point. Below 15% usually means a player is running routes to occupy a defender rather than to catch anything.

How is this different from snap counts?

A snap only says the player was on the field. A tight end can play 95% of snaps and spend most of them blocking, which is why snap share flatters tight ends and backs.

Routes run counts the plays he was actually in the pattern. That makes it the better denominator for any efficiency number, and the better read on how a coaching staff is using someone. The snap count page answers whether he was out there; this one answers what he was doing.

What is target share, and why is it here?

His targets as a percentage of his team's targets that week. It is the volume half of the same question TPRR asks about rate: a receiver can earn targets at a high rate and still see very few if his offense does not throw.

Read them together. High TPRR with low target share is a player being wasted; high target share with low TPRR usually means he is on the field a great deal and the looks are coming to him by default.

Where these numbers come from

Routes and route rate are charted, not derived. No public play-by-play feed records whether a player ran a route, so this comes from a weekly charting export rather than the same source as the rest of the site. That is the reason a weekly routes page is rare.

Route % is route participation, his routes against his team's pass plays that week. That is the number fantasy analysts mean by the term, and it answers how much of the passing game he was actually part of.

It is deliberately NOT the route rate PFF publishes, which divides routes by the pass snaps a player was on the field for. That reads 89% for the median receiver and cannot separate a full-time starter from someone who played eleven snaps and ran a route on all of them. It is a useful number for backs and blocking tight ends and a poor one for this column. Denominator is the most pass plays any charted player on that team saw, which keeps numerator and denominator inside the same charting system.

Rates are suppressed below eight routes. A back who ran three routes and saw one target is not a 33% TPRR receiver in any sense worth sorting on, so TPRR and YPRR are left blank until there is enough behind them. Routes and targets still show.

Target share is measured against the charted pass catchers on each team, which is every receiver, back and tight end who ran a route that week. It lands within a target or two of the true team total and is consistent between players, which is what a share needs to be.

Weeks are graded independently. Nothing here is a season average.