Defensive line, Wake Forest, 2014–16
Chris Stewart
- Number
- No. 96
- Height
- 6′3″
- Hometown
- Petal, MS
Chris Stewart played defensive line at Wake Forest (2014–16).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2016 | Wake Forest | 20 | 12 | 4 | 2.5 | 3 | 2 |
Season lines from CollegeFootballData, regular season and bowls.
Defense before 2016
| Season | G | Solo | Ast | Tkl |
|---|---|---|---|---|
| 2015 | 8 of 12 | 7 | 5 | 12 |
Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources: ESPN play-by-play participants, via SportsDataverse: tackles only, counted in the games whose play-by-play names tacklers (G: those games, of his team’s), so part of the season, not its total. A dash: the source has no number for it.
On the roster
| Season | Team | No. | Pos | Ht |
|---|---|---|---|---|
| 2014 | Wake Forest | 96 | DL | |
| 2015 | Wake Forest | 96 | DL | |
| 2016 | Wake Forest | 96 | DL | 6′3″ |
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
2016 Wake Forest 9 games, 20 tackles, 2.5 sacks
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 1 | vs. Tulane | W 7–3 | 2 | 2 | 1 | 1 | 0 |
| Sep 10 | at Duke | W 24–14 | 1 | 1 | 0 | 0 | 0 |
| Sep 17 | vs. Delaware | W 38–21 | 1 | 1 | 0 | 0 | 0 |
| Oct 1 | at NC State | L 16–33 | 3 | 1 | 0 | 0 | 1 |
| Oct 8 | vs. Syracuse | W 28–9 | 1 | 1 | 1 | 0 | 0 |
| Oct 29 | vs. Army | L 13–21 | 3 | 3 | 0 | 0 | 0 |
| Nov 5 | vs. Virginia | W 27–20 | 4 | 1 | 1 | 0.5 | 2 |
| Nov 12 | at Louisville | L 12–44 | 3 | 1 | 1 | 1 | 0 |
| Nov 26 | vs. Boston College | L 14–17 | 2 | 1 | 0 | 0 | 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.