RB James Starks - Green Bay Packers
|6-2, 218||Born: 2-25-1986||College: Buffalo||Drafted: Round 6|
News you need to know
From the upgrade/downgrade report (Mon Dec 5): Starks was an embarrassment in Week 13, benched in the first half, and possibly banished to a minor role in the backfield for the rest of the season.
Week 14: vs Seattle Seahawks
Mark and Joe say: Bad matchup. The Packers have a problem at running back (especially from a fantasy owners' perspective) - they can't rely on any one back to generate yardage, and are spreading the ball around widely. Last week, Ty Montgomery was the lead running back/wide receiver on the roster, with 6/40/0 on the ground (and three targets for 2/16/0 receiving), while Jeff Janis was second on the team with 1/19/0 rushing. James Starks had a terrible game (4/1/0 rushing and zero targets) while Aaron Ripkowski (again) claimed the lone rushing TD by Green Bay last week (3/14/1 rushing with one target for 1/4/0 receiving). Christine Michael saw nine carries for 19 yards. It's a mess, folks. The Seahawks lead the NFL allowing just 16.2 points per game - something to keep in mind when setting lineups this week. They average 99.2 rushing yards allowed per game, (14th in the NFL) with nine rushing scores given out to date. From Week 10 to Week 13 of regular season (the last four weeks, but includes 10 teams on byes during that time span - each team has at least three games played in the last four weeks), Seattle averages 15.5 fantasy points allowed to opposing running backs per game (11th-least in the NFL). Carolina had 21/89/0 rushing at Seattle last week. This is a bad matchup for the jumbled Packers' backfield.
Recent Stats and Projections
Recent Game Summaries
2016 Week 13 vs HOU (4 / 1 / 0 rush, 0 / 0 / 0 / 0 rec)
Even though Christine Michael was unimpressive as a running back in his Packers debut as a starter, he got nine carries to Starks' four. That's a clear indication that the Packers are not anymore enamored of Starks then they were when they drafted Eddie Lacy and don't trust him as a bellcow back. He looked slow gaining the edge on his first carry and then was stuffed for no gain on his second when all he needed was a yard for a first down. Starks isn't an impressive runner and he did nothing to change that opinion against Houston.
2016 Week 12 vs PHI (17 / 41 / 0 rush, 5 / 5 / 27 / 0 rec)
When will Christine Michael be ready to carry the load, or perhaps when will Eddie Lacy return. Either question is relevant these days as Starks continues to be unimpressive running the ball. On a day when Rodgers was able to throw the ball well, pulling defenders out of the box, Starks still couldn't get anything going. The Packers were relatively committed to the Starks running the ball--with the exception of the second quarter when they called his number just three times the team used Starks consistently during the game. That didn't help him though, as he struggled to find holes, break tackles and make any headway against the Eagles.
2016 Week 11 vs WAS (9 / 25 / 0 rush, 6 / 5 / 46 / 1 rec)
Starks didn't look much different than he did last week and his limitations are pretty evident with his lack of overall speed, athleticism and power on display on every carry. He lacks anything like elusiveness as well, too often brought down by a single tackler. He did have a nice catch and run in the fourth quarter when Washington seemed to forget he was on the field. He was wide open in the flat and Aaron Rodgers had no problem dumping a short pass to him. There was nothing but green between him and the end zone as he ran for the score.
2016 Week 10 vs TEN (7 / 33 / 0 rush, 4 / 3 / 11 / 1 rec)
Starks is still the same guy, a decent runner with little to no top end speed and serviceable vision. The Packers fell behind 21-0 in the first quarter so they abandoned the run game and Starks merely handled receiving duties. Starks did score a nice touchdown on a screen pass, as he ran the ball the extra 13 yards for the score. Even on that play, though, Starks looked plodding and if the Titans had taken better angles he probably would have been caught.
2016 Week 5 vs NYG (12 / 33 / 0 rush, 6 / 3 / 19 / 0 rec)
Every time Starks gets a shot to show what he can do we are reminded what that is: not much. Starks got nine carries and looked decidedly average with all of them. Of course, there is something to be said for getting a back into rhythm and the Packers' use of Starks was a bit all over the place. Still, we've seen Starks run the ball and he's got average speed, little elusiveness and not a ton of power. He also had one of the ugliest fumbles we've seen this year on his last touch of the game. On the play, quarterback Aaron Rodgers hit him over the middle with a short pass. Starks was wide open and made the grab, but when he turned to run with the ball, a defender was right there. It's not totally clear why it happened, but Starks essentially threw the ball to the Giants defender. Luckily for Starks, the defender didn't hold on and Starks was able to recover.
2016 Week 3 vs DET (1 / -1 / 0 rush, 2 / 1 / 9 / 0 rec)
James Starks did well holding Eddie Lacy's coat, as he once again had nothing else to do beyond a few runs to give the starter a breather.
2016 Week 2 vs MIN (7 / 3 / 0 rush, 1 / 1 / 16 / 0 rec)
Starks continues to be nothing but the source of a breather for Eddie Lacy. He gets very little work as more than a blocker and while he was on the field for 30 offensive snaps, that was the role he was in for the majority of them.
2016 Week 1 vs JAX (4 / 7 / 0 rush, 1 / 1 / 6 / 0 rec)
If you were unclear what James Starks would be for this team, this was a clear signal that he gives Eddie Lacy a breather and that's all. Starks had little to do in this game and that will be the case most of the time.
Latest NewsPackers | James Starks faces tough test (Tue Nov 29, 03:22 PM) - Green Bay Packers RB James Starks will be up against a Houston Texans defense in Week 13 that has allowed only 58.8 rushing yards per game since Week 8. The Texans have not allowed a rushing touchdown since then. Our View: The Packers aren't going to run the ball much (or effectively) anyway. On the season, the Texans have the 19th-ranked rush defense allowing an average of 107.5 rushing yards per game. Starks is only a flex option for fantasy owners, and we're not excited about his prospects in Week 13.
link to story Packers | James Starks totals 68 yards (Tue Nov 29, 12:20 AM) - Green Bay Packers RB James Starks rushed 17 times for 41 yards in the Week 12 game against the Philadelphia Eagles Monday, Nov. 28. He also added five receptions for 27 yards on his five targets. link to story
Green Bay Packers Team LinksDepth Chart Season Stats Targets Red Zone Game Logs
Footballguys ArticlesAn Optimal MFL10 Draft, Round by Round
Justin Howe - August 15
Perfect Draft - 12 Team Non-PPR
David Dodds - August 24
Perfect Draft - 12 Team PPR
David Dodds - August 24
How To Attack Large Non-PPR Leagues
Jeff Tefertiller - August 22
How To Attack Large PPR Leagues
Jeff Tefertiller - August 17
2016 Fantasy Football: Early Running Back Top 10
Alessandro Miglio - May 11
Evaluation by Association
Ryan Hester - August 23
Single RB, Part II: The Players You Should Be Targeting
Ryan Hester - August 12
Overvalued Players: Running Backs
FBG Staff - August 24
Training Camp Cliff Notes: Week 2
Joe Bryant - August 17
Articles from around the webHow Vegas Spreads Affect Fantasy Football Running Back Performance
Matt Blair - June 1
Where Were the Biggest Production Gaps For Running Back Duos in 2015?
Dan Pizzuta - June 15
Fantasy football 2016 backfield situations by team
Matt Franciscovich - June 16
Red Zone Notebook
Rich Hribar - June 20
Scott Kacsmar - June 22
Packers Fantasy Preview
Evan Silva - July 4
Fantasy Football Pre-Season Preview: Running Backs
David Dorey - July 26
Silva's Non-PPR Top 150
Evan Silva - August 4
Silva's Updated PPR Top 150
Evan Silva - August 10
Training Camp 2016 Tier Rankings: Week 4
- August 23
|14||vs Seattle Seahawks|
|15||@ Chicago Bears|
|16||vs Minnesota Vikings|
|17||@ Detroit Lions|