Win. Your. League.

Receive 3 Free Downloads More Details

RB Adrian Peterson - Minnesota Vikings

6-0, 220Born: 3-21-1985College: OklahomaDrafted: Round 1, pick 7

Main      Career stats      Game Logs      Game Recaps      Split Stats      Play-by-play      Latest News

Photo: Jeff Curry, US Presswire

Traditional view      FanDuel view      DraftKings view     

Preseason player page

Week 21: bye week

All RB vs

Recent Stats and Projections

WEEKOPPoSNAPRSHYDTDTARGRECYDTDFumLPts
17 at GB 31 19 67 1 1 1 1 0 0 12.8
18 vs SEA 0 23 45 0 2 2 13 0 1 4.8

Recent Game Summaries

2015 Week 18 vs SEA (23 / 45 / 0 rush, 2 / 2 / 13 / 0 rec)

On a day where Adrian Peterson struggled behind an offensive line that seemed to have no answer for the Seahawks run defense, his most impactful play was a terrible one. Next to kicker Blair Walsh's last second shank, no play factored into the Vikings loss more than Peterson's fourth quarter fumble. With just under 11 minutes left, Peterson ran a short out route into the flat where quarterback Teddy Bridgewater hit him with a short pass. Peterson easily made the catch and turned upfield, crossing the first down marker as linebacker K.J. Wright grabbed the arm not holding the football. Close-ups revealed later that Peterson did not have his right hand wrapped around the tip of the football. So when safety Kam Chancellor collided with Peterson and ripped at the football, it's not shocking it came loose. As most NFL fans know, this has been an issue for most of Peterson's career. This season saw the most fumbles since 2009 when he had seven also, and he has 38 total in his career. For most of the rest of the game, the Seahawks spent a lot of time trying to recreate the fumble but Peterson used two hands the rest of the way. Overall, while Peterson had a great season overall (and totaled the third most rushing yards in his career), he struggled mightily behind a shaky offensive line on Sunday and between the fumble and his 2-yards-per-carry average, this is one game he's likely to want to forget.

2015 Week 17 vs GB (19 / 67 / 1 rush, 1 / 1 / 1 / 0 rec)

Aside from a lower-back pain which forced him from the game for most of the fourth quarter, Peterson had an OK game. The offensive line gives him little help, but that hasn't slowed him down all that much even if it often hampers his overall yards per carry. He still manages to make a first down or a big play when the team needs it. Peterson showed his vision and agility on a 10-yard carry in the third quarter where he took the handoff, got skinny and slipped through the hole and quickly got to the second level. He then used a jump cut to avoid another defender, then turned upfield again before being brought down for a first. Peterson also showed tremendous determination on his 3-yard touchdown run. He was held up at the one yard line but kept pushing and bulled his way and kept his legs pumping to the goal line. Peterson will be a huge factor going up against Seattle next week and is going to need some help--either with a pass game to loosen the defense up or better blocking up front- against the front seven of Seattle.

2015 Week 16 vs NYG (22 / 104 / 1 rush, 2 / 1 / 15 / 0 rec)

Peterson didn't look like someone who was hampered by an ankle injury in practice last week as he had success behind an offensive line which did better than usual in clearing lanes for him. He showed off his tremendous jump-cut more than once, and continues to look fast when he gets into the open field. On his touchdown he showed good power and determination, bashing his way to the one and extending the ball for the score. Overall, Peterson looks ready for the playoffs and the expected drop off at the age of thirty seems to have been held off for a year.

2015 Week 15 vs CHI (18 / 63 / 0 rush, 0 / 0 / 0 / 0 rec)

It was a pretty pedestrian day for Peterson, though part of that was due to a sprained ankle which reportedly isn't serious but certainly hampered him after he had it injured in the second quarter. He is expected to play against the Giants on Sunday. In his carries on this Sunday, Peterson started off very effectively, ripping off some 6 and 9 yard runs, but more and more often the Bears met him at the line of scrimmage and stopped him there if not behind it. Peterson was also not used in the pass game Sunday, with Matt Asiata and Jerrick McKinnon filling in.

2015 Week 14 vs ARI (23 / 69 / 1 rush, 1 / 1 / 17 / 0 rec)

During the opening drive, Peterson ran hard and angry, averaging 9.5 yards a carry and capping it off with a touchdown and including a fantastic 21-yard run through the "2" hole which featured a pair of very nifty jump cuts. Peterson then showed great vision and a few nice moves to avoid or break tackles on his 9-yard touchdown run. After that though, Peterson was held up more often than not at the line of scrimmage and he gained just 31 yards on 19 carries with a 1.6 yards per carry average. He still broke a few 6 or 7 yard runs where he showed his ability to get skinny through a tight hole or catch the edge off tackle, but the Cardinals stacked the box on too many downs and hit him at or behind the line of scrimmage, which limited his overall impact for the second game in a row.

2015 Week 13 vs SEA (8 / 18 / 0 rush, 4 / 4 / 6 / 0 rec)

The Seattle Seahawks came ready to shut Adrian Peterson down, and they did just that, hitting him at or behind the line of scrimmage constantly and swarming him to bring him down and limit his ability to gain yards. Peterson was more effective receiving as he could get the ball in space and gain some extra yards. For the most part though, he was stymied. He also spent much of the game on the sidelines as the Vikings fell behind early and had to throw the ball. After the game, Peterson was asked if it was just a bad day. "I felt like we were out of sync," he responded per the Vikings PR release and game notes. "Definitely give credit to Seattle; they did a good job of coming in and forcing us to do things differently. They were just the better team. They were more aggressive, more physical, and they outcoached us as well." Peterson, not comfortable out of the pistol or shotgun, was often on the sidelines when those formations were called for. That didn't sit well with Peterson. "I felt like, as one of the leaders on the team, and seeing how the running game has been all season, you definitely want to be able to go out and establish the run and then let things feed off of that. I finished with eight carries, and it's tough. I feel like we need to sit back and evaluate some things again and get back to where we need to be."

2015 Week 12 vs ATL (29 / 158 / 2 rush, 4 / 2 / 29 / 0 rec)

Even the No. 1 rushing defense could only contain Peterson for so long, as he wore them down over the course of his 29 carries. After averaging 4 yards a carry in the first half his average jumped to 6.47 as he wore the Falcons down. Throughout the game, Peterson showed his usual burst, overall speed and vision, coupled with a sharp jump cut and great instincts. He repeatedly found ways to gain yards where there seemed to be none, and most impressive is his ability to "get skinny" and fit through tight holes at the line. While Peterson bulled his way to a touchdown early in the game, it was his 35-yard touchdown with really broke the Falcons' back. On the play, Peterson took a pitch and took the ball left towards the edge of the offensive line. Peterson then planted his foot and headed upfield. He was so quick he blew past a defender who appeared to have a perfect angle, then cut to the sideline and accelerated for an easy score. It was his final carry of the day and a perfect way to cap off a win. According to NFL.com's Gil Brandt, Peterson because the sixth player NFL history with 30 games of 125 or more rushing yards.

2015 Week 11 vs GB (13 / 45 / 1 rush, 2 / 2 / 16 / 0 rec)

The solution to the offensive line woes the last few weeks has been to feed the all to Adrian Peterson, but that didn't quite go to plan this weekend. At first, Peterson looked like he had the Packers' number, with runs like the one he bounced outside late in the first quarter, where he looked as quick and nimble as he ever has. However, the Green Bay defensive line started imposing their will upon the offensive line of the Vikings, and Peterson started to see a lot of traffic in the backfield before he could react or find his hole. Peterson did have a nice touchdown in the late third quarter as he took the ball off-tackle, jukes the linebacker and dragged another defender into the end zone. The problem became, the Packers took a huge lead and Peterson just stopped being effective because of the offensive line issues, so Peterson didn't see much work after the half.

2015 Week 10 vs OAK (26 / 203 / 1 rush, 3 / 2 / 13 / 0 rec)

Even at age 30, Adrian Peterson is relentless, highly motivated and plays with a chip (maybe a whole 2 by 4) on his shoulder. Peterson was the main weapon in this offense, especially as the Raiders worked were able to shut down the receivers and limit where Teddy Bridgewater could throw. Peterson continues to show tremendous speed, a first-rate jump-cut and the ability to see the seams in a defensive front which allows him to break free and gain yards regardless of how many guys are in the "box." Once the Vikings decided to grind the clock down with Peterson, the Raiders focused on stepping up the safeties to play the run and stack the front line with as many defenders as they could. The problem with that is, if a running back like Peterson gets behind that front seven, it's a disaster. That's exactly what happened with 1:50 left in the game with the Vikings trying to kill the clock, up 23-14. On the play, the Raiders had seven men in the "box," with a safety just a shade back from the front, but who stepped up immediately when he saw Peterson with the ball. The result was nine players at the line of scrimmage after the snap, with one cornerback on a receiver and another playing contain on the opposite side. Peterson took the snap and went off the right tackle, moving too quickly for the corner to react and leaving him grasping at air. Once Peterson was past that guy, it was over--there was nobody left to even come close to tackling him and he was gone for an 80-yard touchdown.

2015 Week 9 vs STL (29 / 125 / 1 rush, 2 / 2 / 18 / 0 rec)

It was a record-setting kind of day for Adrian Peterson as as this was the 100th game he has led the team in rushing yards, became only the sixth player to have 90 rushing touchdowns in his first nine NFL seasons and moves into ninth place All-Time for most 100 yard rushing games in the first nine NFL seasons as well with 46 (all per Vikings PR/Game Notes). The Vikings took an interesting approach on Sunday, one which they haven't really tried before. Rather than pound with Peterson early, wearing the defense down and hopefully opening passing lanes for the offense, they threw the ball often early on in an effort to take advantage of the stacked fronts Peterson tends to face. The idea was to 'throw the lanes open' and force the defense to respect the pass in order to help Peterson get more room to run. For the most part, it worked and Peterson was able to gain yards at an average of 4.3 yards a carry. His touchdown was very straightforward, as Peterson took the ball deep in the backfield and ran to the edge on the right side of the line. The offensive line did a nice job of blocking for him and he was easily able to zip into the end zone untouched. Peterson ended up basically having his way against a defensive front missing Robert Quinn, Chris Long and TJ McDonald. While he would have likely still had a solid day, the lack of those playmakers made his life a lot easier, especially down the stretch. When Teddy Bridgewater left the game with a concussion, the Rams once again tried to stack the box against Peterson, but he put the offense on his back and kept the chains moving.

2015 Week 8 vs CHI (20 / 103 / 0 rush, 2 / 2 / 6 / 0 rec)

A lot has been said in media and on Twitter about how Peterson doesn't look the same and isn't as good as he used to be. After three sub-100 yard efforts in a row with only one touchdown, perhaps that's understandable, though Kansas City is ranked 13 in DVOA against the run at Football Outsiders and Denver is, well Denver. Still if you were worried Peterson didn't have 'it' anymore, you might be graying your hair for no reason. Peterson looked as good as ever against an admittedly awful run defense, averaging 5.2 yards per carry, hitting the holes hard and slipping past defenders with ease. One of his better runs was a 12-yard effort in the second quarter. Peterson's prior two carries were for 9 yards and 11 yards, and the offense was lined up with a fullback and Peterson in the backfield, so it was fairly obvious this was going to be a run play. The Bears rushed four and then brought the outside linebackers on a delayed rush to contain the outside. Peterson got the ball and made one defender who had gotten into the backfield already, miss. He then broke right to the outside edge, only to see the linebacker and corner lurking. Stopping and changing direction on a dime, Peterson cut back inside as he made another defender miss then accelerated through the hole there. Peterson made another player miss with a nice cut, then got a few more yards before he was brought down. It was a classic Peterson play--it showed speed, vision and quickness and resulted in a large gain. No matter how many defenders the Bears brought into the box, Peterson pushed them back and he only had one negative yards carry (a loss of two in the second quarter) all day. Peterson did most of his damage in the second quarter where he ran for an average of 7.1 yards per carry, though he also broke off a nice 9-yard run just before the Vikings kicked a game winning field goal in the fourth quarter.

2015 Week 7 vs DET (19 / 98 / 0 rush, 3 / 3 / 12 / 0 rec)

The offensive line which gave the passing offense some issues caused problems for Adrian Peterson as well on Sunday. While his final stats were OK, the majority of the day saw him getting hammered at--or more often, behind--the line of scrimmage. Statistically, his day was saved by a 75-yard run in the third quarter, though you can argue that this was the result of the constant runs which wore the defense down. On the play, Peterson took the ball in the backfield and made the defensive end miss with a nice jump-cut. He then ran to the left sideline and accelerated along it. After making Lions safety Glover Quin miss, he was hauled down by Ziggy Ansah just short of the touchdown. Peterson also caught the ball and several times was lined up as a wide receiver.

2015 Week 6 vs KC (26 / 60 / 0 rush, 1 / 1 / -3 / 0 rec)

The Kansas City Chiefs decided it was Teddy Bridgewater or nobody who beat them Sunday and as that was the plan, they stacked the line to stop Adrian Peterson. The Chiefs lined up five men at the line of scrimmage on any play they suspected might involve Peterson, and usually had another two or three men in the box as well. On top of this, the offensive line struggled especially on the right side. So there were often defenders in the backfield as Bridgewater was handing Peterson the ball. All in all, it was a long day for Peterson, though he has adjusted and overcome such things before. For his own part, Peterson was satisfied that he could free things up for the passing game. "That's what it's all about," he said according to the team's PR department release. "Forcing the team to pick their poison. You're either going to stop the run or the pass, and they chose the run today. It opened it up for us in the passing game, and we were able to be productive and get some points on the board." As long as the Vikings can keep taking advantage of that, Peterson will continue to be a weapon.

2015 Week 4 vs DEN (16 / 81 / 1 rush, 6 / 4 / 13 / 0 rec)

Adrian Peterson struggled for most of the game, until he broke free for a 48-yard touchdown run. The play was almost too easy, as the Broncos crowded the line with nine players on 4th and 1. Peterson ran through the '1' hole without being touched and was immediately in open space, as all the defenders were caught at the line. He swiftly blew past the safety and ran the rest of the way for a score. On the downside, Peterson continues to be hit or miss in pass protection, and on the last offensive play of the game it cost the Vikings. On the play, quarterback Teddy Bridgewater dropped back and was blindsided by Denver safety TJ Ward. There was some debate as to whether Peterson, who started the play in the backfield, should have picked up Ward. In the end, ESPN's Ben Goessling tweeted out that it was Peterson's responsibility. By letting Ward by without touching him, he allowed Bridgewater to get hammered, fumbling the ball and effectively sealing the loss. Offensive coordinator Norv Turner has wanted to keep Peterson on the field for passing downs, but if he cannot be counted on to block--especially behind a patchwork offensive line--then he cannot be on the field.

2015 Week 3 vs SD (20 / 126 / 2 rush, 0 / 0 / 0 / 0 rec)

Peterson was everything his owners could have hoped for in this game. The Vikings used him heavily on early downs to keep the offense on schedule, he was running with great power, conviction, and downhill cuts, and Peterson generally kept the Chargers defense on their heels as the game went on. Peterson's piece de resistance in this game was a 40+ yard touchdown run that included a stiff arm, a broken tackle, a cut back against the grain from the sideline and the final kick to score. He also finished a drive in the first half with short score and was barely short of a third score in the second half. He seems to be the centerpiece of the offense and an elite RB1 going forward.

2015 Week 2 vs DET (29 / 134 / 0 rush, 2 / 2 / 58 / 0 rec)

The first notable difference between this game and the Week 1 debacle against the San Francisco 49ers was how offensive coordinator Norv Turner and head coach Mike Zimmer moved away from having Adrian Peterson take handoffs in the shotgun. Last week that caused issues for Peterson, so they went back to the old way of doing things to get him into a rhythm during his first four carries. The result on those runs totaled 38 yards and got him warmed up, so when he took some carries out of the shotgun formation, he didn't lose momentum. He looked far more comfortable on those carries as well, though the Detroit Lions seemed to have an easier time getting through the offensive line and slowing Peterson down when the Vikings were in that formation. Overall, Peterson looked much closer to the player we expected than he did last week. He showed good vision, speed and strength in his runs and seemed much more comfortable than he did in Week 1. One of his best runs came with two minutes left in the first and Minnesota leading 7-0 and the offense on a 2nd-1 at Detroit's 42. The play called for Peterson to run up the middle, but it was instantaneously clear that there was no room there. Peterson immediately bounced out of the middle and ran off the right tackle, getting North-South as soon as possible to get the first. The run showed all the savvy and field awareness we've come to expect from him. Peterson also helped quarterback Teddy Bridgewater turn a disaster into a great play, though his poor block was part of the reason Bridgewater was almost sacked. On the play, Peterson held up defensive tackle Tyrunn Walker only briefly and the tackle quickly moved to take down Bridgewater. While trying not to fall, Bridgewater tossed a little underhand throw to Peterson who then took the ball 49 yards. The team has tried to get Peterson more involved in the pass game as a receiver, but he's going to have to improve his blocking or else the team will need a better blocker in there on passing downs. He's also got to protect the ball a little better as he had it knocked loose in the early third quarter. Luckily, the Lions were so inept on offense Sunday that they did nothing with the opportunity.

2015 Week 1 vs SF (10 / 31 / 0 rush, 3 / 3 / 21 / 0 rec)

As was the case with quarterback Teddy Bridgewater, Adrian Peterson clearly suffered because of poor play along the offensive line. He was frequently met at or behind the line of scrimmage by one or more defenders, and rarely seemed to be able to get up to full speed. Normally, this wouldn't slow Peterson down--certainly he has played behind bad offensive lines before--however, he is also dealing with a new offense, one focused on the quarterback not Peterson. That was certainly an issue according to Mark Craig of the Star-Tribune, who reported that Peterson didn't feel right taking handoffs in the shotgun formation. When things went smoothly, Peterson looked just as effective as he has in years past--those moments were just few and far between. Peterson had no carries in the fourth quarter.

More

Minnesota Vikings Team Links

Depth Chart      Season Stats      Targets      Red Zone      Game Logs

Footballguys Articles

What if Adrian Peterson is Lost for the Season?
  Phil Alexander - August 25
Melvin Gordon, Todd Gurley, and a Brief History of Rookie RBs
  Justin Bonnema - May 27
The Contrarian: FanDuel Week 7
  Justin Bonnema - October 23
The Fade: FanDuel Week 1
  Justin Bonnema - September 11
The Fade: FandDuel Week 3
  Justin Bonnema - September 24
The Fade: FanDuel Week 6
  Justin Bonnema - October 16
Gameday Injury Expectations: Week 7
  Jene Bramel - October 25
Hidden Value or Damaged Goods
  Jene Bramel - August 30
Reading the Defense: Defensive Line Tiers
  Jene Bramel - August 20
Reading the Defense: Defensive Line Tiers
  Jene Bramel - September 2

Articles from around the web

2015 NFL Coaching Turnover and Fantasy Football Implications
  John Paulsen - March 26
32 Fantasy Questions: Northern Divisions
  Pat Thorman - May 19
The 2015 Rankings Breakdown
  John Paulsen - May 19
Four Downs: NFC North
  Sterling Xie - May 22
Fantasy predictions with huge repercussions (if wrong)
  Michael Fabiano - May 26
32 Fantasy Questions: Western Divisions
  Pat Thorman - May 29
Which teams gained and lost the most rushing production this off-season?
  Will Laws - June 1
Prisco's Top 100
  Pete Prisco - June 2
The Top 10 Seasons for Running Backs 30 and Over
  Mark Zelenko - June 2
AP's Back! Now What?
  John Tuvey - June 4

Schedule