Skip to main content
parlae.ioBeta
Sign in

Trade Ashton Jeanty for Jonathan Taylor? Yes, Taylor is worth 25 more.

Yes on value. Jonathan Taylor is worth 120 rest of season and Ashton Jeanty 95, so the side getting Taylor gains 25. Jeanty rates 16.5 market points a game with 11 games left, Taylor 18.8 with 11. On usage, Jeanty has 70 percent of LV carries and 18 percent of its targets; Taylor has 77 percent of IND carries and 12 percent of its targets. Jeanty hosts BUF in Week 6 (6th most points allowed to RBs); Taylor hosts TEN in Week 6 (14th fewest points allowed to RBs). Neither carries an injury designation this week.

The verdict, Week 5

Getting Jonathan Taylor wins by 25.

Ashton Jeanty 95120 Jonathan Taylor

Run this trade in the analyzer

Both sides are filled in. Add a player to either side to check a two for one.

See it against your lineup

Sync your league and the analyzer shows your best starting lineup before and after the deal. Free, no account.

95

value, #13

Pts/game
16.5
Games left
11
Bye
13
Ashton Jeanty weekly market-based points
Wk 3Wk 4Wk 5
16.716.216.5

120

value, #5

Pts/game
18.8
Games left
11
Bye
13
Jonathan Taylor weekly market-based points
Wk 3Wk 4Wk 5
18.120.518.8

Where the values come from

Jeanty is the 10th running back on the chart and 13th overall. His 16.5 a game is 8.6 above the replacement running back's 7.9, over 11 games left with his bye in Week 13, which is how he comes to 95.

Taylor is the 4th running back on the chart and 5th overall. His 18.8 a game is 10.9 above the replacement running back's 7.9, over 11 games left with his bye in Week 13, which is how he comes to 120.

The weekly market prices

The market priced Ashton Jeanty at 16.7 in Week 3, 16.2 in Week 4 and 16.5 in Week 5, a median of 16.5 points a game, flat across them.

The market priced Jonathan Taylor at 18.1 in Week 3, 20.5 in Week 4 and 18.8 in Week 5, a median of 18.8 points a game, up 0.6 from his first frozen week to his latest.

Advertisement

Points so far against the price

Ashton Jeanty has scored 84.6 PPR points in 5 games, 16.9 a game, level with the 16.5 the market prices him at from here.

Last season he finished RB11 with 245.1 PPR points in 17 games, 14.4 a game.

Week 1 vs MIA: 32.7 points (RB4 that week), 102 rushing yards on 23 carries, 6 of 6 targets for 45 yards, 2 touchdowns, 74 percent of snaps.

Week 2 vs LAC: 10.3 points (RB23 that week), 48 rushing yards on 21 carries, 4 of 7 targets for 15 yards, 81 percent of snaps.

Week 3 vs NO: 12.3 points (RB18 that week), 56 rushing yards on 19 carries, 3 of 3 targets for 37 yards, 84 percent of snaps.

Week 4 vs KC: 18.6 points (RB14 that week), 58 rushing yards on 15 carries, 6 of 8 targets for 68 yards, 67 percent of snaps.

Week 5 vs NE: 10.7 points (RB23 that week), 27 rushing yards on 10 carries, 3 of 6 targets for 50 yards.

Jonathan Taylor has scored 97.4 PPR points in 5 games, 19.5 a game, 0.7 a game more than the 18.8 the market prices him at from here.

Last season he finished RB4 with 362.3 PPR points in 17 games, 21.3 a game.

Week 1 vs BAL: 25.1 points (RB8 that week), 98 rushing yards on 19 carries, 3 of 4 targets for 23 yards, 2 touchdowns, 89 percent of snaps.

Week 2 vs KC: 29.2 points (RB1 that week), 92 rushing yards on 24 carries, 4 of 4 targets for 40 yards, 2 touchdowns, 94 percent of snaps.

Week 3 vs HOU: 9.2 points (RB27 that week), 68 rushing yards on 23 carries, 2 of 3 targets for 4 yards, 85 percent of snaps.

Week 4 vs WAS: 22.7 points (RB10 that week), 95 rushing yards on 20 carries, 1 of 4 targets for 2 yards, 2 touchdowns, 71 percent of snaps.

Week 5 vs PIT: 11.2 points (RB22 that week), 45 rushing yards on 15 carries, 3 of 4 targets for 37 yards.

Usage a game this season

Through Week 4, Ashton Jeanty has averaged 19.5 carries for 66 yards and 6.0 targets and 4.8 catches for 41 yards a game on 76 percent of the snaps.

He has been targeted or handed the ball 21 times inside the 20, 54 percent of his team's chances there, and has scored 2 touchdowns in 4 games.

In Week 4 against KC he had 15 carries and 8 targets on 67 percent of the snaps.

Through Week 4, Jonathan Taylor has averaged 21.5 carries for 88 yards and 3.8 targets and 2.5 catches for 17 yards a game on 84 percent of the snaps.

He has been targeted or handed the ball 17 times inside the 20, 47 percent of his team's chances there, and has scored 6 touchdowns in 4 games.

In Week 4 against WAS he had 20 carries and 4 targets on 71 percent of the snaps.

Schedule and next matchup

A trade made now buys Week 6 through Week 17. Ashton Jeanty has 11 games in it with his bye in Week 13; Jonathan Taylor has 11 games with his bye in Week 13.

BUF, Jeanty's Week 6 opponent, has allowed 26.3 PPR points a game to RBs this season over 4 games, the 6th most to RBs of 32.

TEN, Taylor's Week 6 opponent, has allowed 20.6 PPR points a game to RBs this season over 4 games, the 14th fewest to RBs of 32.

What would even it

The side getting Ashton Jeanty would want about 25 more added to make it even: a player like Sam LaPorta, valued at 25. Two players for Taylor also costs that side a roster spot.

Sam LaPorta's player page

The full Week 5 trade value chart

Common questions

  • Should I trade Ashton Jeanty for Jonathan Taylor?

    Yes on value: Jonathan Taylor is worth 120 and Ashton Jeanty 95, a gain of 25. If Ashton Jeanty starts for you and Jonathan Taylor would sit, check the lineup first in the trade analyzer.

  • Who has more rest-of-season value, Ashton Jeanty or Jonathan Taylor?

    Jonathan Taylor, 120 to 95. He rates 18.8 market points a game over 11 games left, against 16.5 over 11 for Ashton Jeanty, each measured above a replacement starter at his own position.

  • How are these trade values calculated?

    Each player's points per game is the median of the market-based PPR points we froze before each week's first kickoff, Weeks 3, 4, 5. A replacement starter's rate is subtracted and the rest is multiplied by his games from Week 6 to Week 17, bye taken out. No expert opinion is involved.

By the Parlae deskValues updated Oct 12, 2026 at 9:06 AM ETHow this is builtReport a wrong number