Rushing Yards vs. Rushing Attempts: Which NFL Prop Is More Predictable?
Rushing attempts (the same thing as carries) are usually the steadier of the two, as a rule of thumb. A carry count tracks a back's role and how the game script unfolds. Rushing yards aren't as simple. They depend on that same workload and on how explosive each carry turns out to be, and one long run can swing a yardage line without moving the carry count at all.
By Prop Lab
Side by Side
| Factor | Rushing Attempts | Rushing Yards |
|---|---|---|
| What it counts | Carries | Total rushing yardage |
| Main driver | Carry share and game script | Carries × yards per carry |
| Extra source of variance | None beyond workload | Explosive plays, yards after contact |
| Most sensitive to | Role, game script, goal-line work | Game script, plus one or two long runs |
| Steadier week to week | Yes | Less so |
Why Attempts Track Role and Game Script
Rushing attempts count carries, including quarterback scrambles and kneel-downs, whether they gain or lose yards. Sacks do not count. That's what makes a running back's attempt total mostly a role stat. It tracks how big a share of the backfield's carries a back gets, what the industry calls his carry share, and how the game script plays out. A team that's protecting a lead in the fourth quarter tends to run more to burn clock, which lifts attempts even when the yards per carry aren't great. A one-yard dive and a fifteen-yard burst each count as exactly one attempt, so the number doesn't care how far the ball's gone.
Why Rushing Yards Carry More Variance
Rushing yards are, in effect, attempts multiplied by yards per carry. The first factor's the same workload that drives the attempt total. The second's where the extra noise enters, yards per carry. A single explosive play such as a broken tackle or a missed angle can carry a big share of a game's total. A back can get his usual number of carries and still land well over or under his yardage line, and it's all down to whether the blocking sprung a couple of long runs or every carry got swallowed up short.
A Worked Example
Say Jonathan Taylor gets a similar number of carries in two different weeks. The numbers below aren't real, just made up to show the idea.
| Week | Attempts | Rushing Yards |
|---|---|---|
| Week 1 | 18 | 74 |
| Week 2 | 19 | 151 |
The carry count barely moves, up one from 18 to 19. The yardage nearly doubles, because Week 2's got one long touchdown run instead of Week 1's carries mostly getting stopped near the line. That's the split: attempts caught the workload, and rushing yards caught the explosiveness.
What to Check Before Researching Either
You're weighing the same opportunity-versus-efficiency split described above, just for a running back. Start with carry share: how many of the team's carries go to this back instead of a committee partner, and whether that share's trending up or down. A committee backfield or a change-of-pace back stealing passing-down work matters more for attempts than for yards. Then there's the goal-line role, since a short-yardage back can score touchdowns without piling up yardage. Then check the expected game script. A team that's favored to lead tends to protect it by running the ball late, while a team expected to trail leans on the pass and only racks up carries in garbage time once the outcome's decided. See how the spread and total shape player props for how the point spread feeds into that read, and how to read NFL usage stats for props for how carry share's tracked week to week. Browse current rushing yards and rushing attempts lines to see where the market's currently sitting.
Sources
- NFL Guide for Statisticians defines how rushing attempts and rushing yards are credited in a game, including that a quarterback's scramble counts as his own attempt. It doesn't count as the running back's. See Rushing, pages 11–12.
- nflfastR publishes open play-by-play data as part of the community nflverse project, and that's where the down, distance, and score-differential detail comes from for studying how game script shapes a carry total.
This Week's Rushing Yards and Rushing Attempts Lines
See every prop this weekWeek 7's biggest line moves, live from the board.
| Player | Matchup | Kickoff | Open | Current | Move | AI pick |
|---|---|---|---|---|---|---|
| Saquon BarkleyRushing Yards · RB · Philadelphia Eagles | vs Dallas Cowboys | Mon 7:15 PM CT | 76.5 | 64.5 | -12 | Pro |
| Dameon PierceRushing Yards · RB · Philadelphia Eagles | vs Dallas Cowboys | Mon 7:15 PM CT | 15 | 19.5 | +4.5 | Pro |
| Javonte WilliamsRushing Yards · RB · Dallas Cowboys | @ Philadelphia Eagles | Mon 7:15 PM CT | 66.5 | 63.5 | -3 | Pro |
| Tyler GoodsonRushing Yards · RB · Dallas Cowboys | @ Philadelphia Eagles | Mon 7:15 PM CT | 10.5 | 13.5 | +3 | Pro |
| Tanner McKeeRushing Yards · QB · Philadelphia Eagles | vs Dallas Cowboys | Mon 7:15 PM CT | 7.5 | 4.5 | -3 | Pro |
Rushing Yards vs. Rushing Attempts FAQ
Get the AI Analyst's Read on Every Prop
Every prop on this week's board gets a side and a write-up from our AI Analyst. Pro gives you all of them.
Pro
First week free
Every prop, picked and explained.
- A side on every prop, plus how strongly the AI Analyst feels about it
- A write-up on each one built on advanced analytics, plus the matchup, injuries, the playcaller, and the weather
- Picks that update through the week as lines move and news breaks
- Command Center, one screen with the AI's top picks of the week, who's on a hot streak, and your Watchlist
- Watchlist, which shows you when a saved prop's line or pick changes
- Full player and team stats, trends, and injury reports
On the Weekly and 5-Week plans. Cancel before the deadline in your account and you won't be charged. See plans and prices
Free account
No card needed. Upgrade whenever you want.
- Every prop we track and how far its line has moved
- Sportsbook odds, our projection, and the Projection Gap
- Previews of stats, trends, and injury reports
See every pick before kickoff
Start your free week to get the AI Analyst's pick and write-up on every prop. Not sure yet? Take the tour and see the app first.
