Defensive end, Auburn, 2010–13
Craig Sanders
- Number
- No. 13
- Height
- 6′4″
- Hometown
- Clio, AL
Craig Sanders played defensive end at Auburn (2010–13).
Team titles: National champions, 2010; SEC champions, 2010 and 2013
Returns
Season lines from CollegeFootballData, regular season and bowls. * That team-season’s player lines are missing part of the team’s yards in our source, so these numbers may be short.
Defense before 2016
| Season | G | Solo | Ast | Tkl | TFL | Sacks | FF | Hur |
|---|---|---|---|---|---|---|---|---|
| 2010 | 8 | 7 | 1 | 8 | 1 | 1 | 0 | 0 |
| 2011 | 10 | 10 | 3 | 13 | 4.5 | 1 | 1 | 3 |
| 2012 | 6 | 6 | 3 | 9 | 1.5 | 0 | 0 | 0 |
| 2013N | 13 | 13 | 9 | 22 | 3 | 0.5 | 0 | – |
| On file | 36 | 16 | 52 | 10 | 2.5 | 1 | – | |
Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources, marked by season: unmarked, cfbstats.com (Open Data Commons Attribution License), its game lines summed (G: the games he has a line in); N, NCAA statistics, via octonion/football, the season’s official lines (G: games played). A dash: the source has no number for it.
On the roster
As each season’s roster listed the player (CollegeFootballData). Classes before the latest listing are counted back from it; “Yr 1” is the year on file where that count can’t place a season he played (a redshirt, transfer or 2020 year); height and weight as last listed.
Game by game
2013 Auburn 1 game, 1 return, 14 yards
| Date | Opponent | Result | KR | Yds | TD |
|---|---|---|---|---|---|
| Oct 12 | vs. Western Carolina | W 62–3 | 1 | 14 | 0 |
2012 Auburn 1 game, 1 return, 10 yards
| Date | Opponent | Result | KR | Yds | TD |
|---|---|---|---|---|---|
| Sep 8 | at Mississippi State | L 10–28 | 1 | 10 | 0 |
2011 Auburn 2 games, 2 returns, 14 yards
2010 Auburn 1 game, 2 returns, 32 yards
| Date | Opponent | Result | KR | Yds | TD |
|---|---|---|---|---|---|
| Nov 6 | vs. Chattanooga | W 62–24 | 2 | 32 | 0 |
Box scores from CollegeFootballData, 2004 on. ✦ postseason; ★ a career high on file.
Is this you, or do you know of something wrong or missing here? Suggest a correction. We check each one against a source before changing the page.