First off, where the hell did Adrian Peterson come from? A guy who was only supposed to carry the ball a minimum of 10 times played like he never even had a knee injury. I swear this guy is robotic. Toby Gerhart owners, myself being one of them, didn't enjoy that switcharoo. In Kansas City, it looks like Peyton Hillis won't have as big a role as we thought. After touching the ball a total of 10 times, the Chiefs put Hillis on the bench once Atlanta jumped out to a big lead. Will this change when the Chiefs face the Bills? Or will Jamaal Charles make his fantasy owners thank him for drafting him as a borderline RB1?
Will Alfred Morris keep the starting job going forward after plodding his way to 98 yards against the Saints? It wasn't exactly a stellar effort, but Mike Shanahan gave his full endorsement to Morris after the game. Maybe we could see Morris put up a similar game against a hurting Rams run defense. Biggest mistake I am sure most owners made was throw DeAngelo Williams in, what was supposed to be an excellent matchup, against a horrible Buccaneers Defense. Jonathan Stewart got more yards sitting on the bench after D-Will managed a meager -1. Are the Bucs for real? Or has the league finally caught up to Cam Newton and the Panthers offense as a whole?
With all that said, lets get to the Week Two Running Back Rankings. Keep in mind to check often as injuries continue to pour in through the week. Also, make sure to check the rest of our rankings for Week Two on our Rankings Page.
Update (9/14): There is a possibility that the Chargers may hold Ryan Mathews (clavicle) out this week against the Titans after Norv Turner was noncommittal about his availability. Looks like owners may have to wait yet another week, maybe two, before Mathews comes back. Use other options if possible.
[table id=190 /]
And there you have it; the Week Two Running Back Rankings. Last week's rankings were fairly accurate and we should only get better with our weekly fantasy rankings as the season goes on.