James Starks: Packers Backup RB Shouldn't Be on Fantasy Radars
Unless you are in a 16-team league or get bonuses for having players named James Starks, James Starks shouldn't be on your fantasy radar.
I understand the temptation will be there, especially after Cedric Benson left Sunday's game and will likely be a huge question mark for next week (via the Green Bay Press-Gazette's Rob Demovsky):
Raji walked out of the locker room with limp, Benson walked out in a boot.— Rob Demovsky (@RobDemovsky) October 7, 2012
But still, James Starks is no Iron Man.
The third-year running back definitely showed potential last season, rushing for 4.3 yards per carry on 133 attempts, but a nagging turf toe has kept him on the sideline for Green Bay's first five games of 2012.
Even if Benson should miss time, Starks, who is obviously less than 100 percent and currently doesn't have a role in this offense, isn't the backup you want to own.
That would be second-year back Alex Green. He's done next to nothing in his career, but proved on Sunday with his nine-carry, 55-yard effort that he is more than capable of filling in for Benson.
Starks may have the experience edge on Green, but there's no way he would step into a full role right away. At the very best, he would earn a timeshare in Week 6.
And by timeshare, I mean fantasy hell.
How many carries will James Starks receive in Week 6?
When it comes down to it, you want to avoid Green Bay's backfield no matter who fills in for Cedric Benson—not to mention we don't even know Benson's status for next week.
Who wouldn't with Aaron Rodgers under center?
Even if you're desperate at running back, 8-to-10 likely inefficient carries—at most—from James Starks probably aren't going to dig you out of the hole.
Move along. Nothing to see here.
What is the duplicate article?
Why is this article offensive?
Where is this article plagiarized from?
Why is this article poorly edited?