What stats matter for NFL rushing yards props?

Carries and snap share come first, followed by efficiency, the defence and the sample behind the numbers. A rushing average is much easier to read when you know how many attempts produced it.

Separate chances from yards gained per chance

Rushing yards are the result. Carries count the attempts. Snap share is the percentage of the team’s offensive snaps the player took, which adds context to that attempt count.

Read those game by game. A back can play plenty of snaps while receiving the ball or protecting the quarterback. A teammate returning to the lineup can change the division of carries even when the player’s season average barely moves.

Then read yards per carry. Across a window, divide total rushing yards by total carries. Averaging each game’s yards-per-carry figure gives a small workload the same weight as a large one.

A real four-game example

These are Derrick Henry’s four completed 2026 games in our October 9 export. The export is dated; it is not a forecast for his next game.

That is 89 carries for 374 yards. Per game, 22.25 carries and 93.5 yards. Per carry, 4.20 yards.

The 26-carry game produced fewer yards than the 24-carry game. Workload alone does not explain the result, but neither does the 93.5-yard average tell you how much work he had.

For a simple illustration, 20 carries at four yards per carry produces 80 yards. Fifteen at the same rate produces 60. That arithmetic explains why a change in workload matters; it assumes an efficiency rate and is not a prediction of either workload.

Read the distribution, not just the average

The same four rows range from 68 to 144 yards. Look at each result and its longest rush before treating the mean as a typical afternoon. One long run can move the final total considerably.

Then ask whether the usage is still comparable. Changes in the backfield, an injury restriction or a different offensive role can make old rows less relevant. Our game log describes what happened; a missing availability update is something to check, not something the average fills in.

Match the defence to the player’s role

On a player’s Head to Head tab, the Same role vs block for that opponent shows the comparable role’s past games against that defence, with carries beside the rushing yards. Read those carries before calling the defence favourable or difficult. A low-yardage result on a small workload asks a different question from the same result on a large workload.

Keep the comparison season visible. Past roles are assigned using usage before that game, and the current role can use today’s main yardage lines. The label is a way to choose comparable rows, not a promise that every player in them received the same workload.

For every defense’s season so far, NFL Defense vs Position shows the carries and rushing yards each team has allowed to running backs, with the game count beside each figure.

Check the window and the market

An L5 can include last season early in the year. Can you trust an NFL player’s L5 early in the season? shows why the dates underneath it matter.

Also keep rushing yards separate from rush plus receiving yards. Total touches can help explain a role, but receptions do not become carries and receiving yards do not become rushing yards.

This four-game example is a reading method. We have not measured which of these inputs adds predictive value beyond a posted rushing line, and no probability or fair price is estimated here.

Source: Steezanomics’ October 9, 2026 NFL export, four Henry games from September 13 through October 4. Season totals above use those four rows only.

Open Derrick Henry’s rushing yards page in the Lab on a day his next game is on the board. The Game Log tab lists each game’s rushing yards against the line, and the Head to Head tab’s Same role vs block shows the comparable backs’ carries and yards per carry beside their yards. Between games his page keeps the game log without a line. For another player, start on the Lab board and select NFL, then RUSH YDS.