Defensive line, SMU, 2012–16
Jarvis Pruitt
- Number
- No. 34
- Height
- 6′3″
- Hometown
- Houston, TX
Jarvis Pruitt played defensive line at SMU (2012–16).
Career highs
3sacks, career highvs. Houston, 2016Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2016 | SMU | 19 | 14 | 5.5 | 4.5 | 0 | 2 |
Season lines from CollegeFootballData, regular season and bowls.
Defense before 2016
| Season | G | Solo | Ast | Tkl |
|---|---|---|---|---|
| 2013N | 10 | 2 | 1 | 3 |
| 2014E | 8 of 12 | 4 | 2 | 6 |
| 2015E | 8 of 12 | 7 | 0 | 7 |
Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources, marked by season: N, NCAA statistics, via octonion/football, the season’s official lines (G: games played); E, 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
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 SMU 9 games, 19 tackles, 4.5 sacks
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 10 | at Baylor | L 13–40 | 1 | 1 | 0 | 0 | 0 |
| Sep 23 | vs. TCU | L 3–33 | 1 | 0 | 0 | 0 | 0 |
| Oct 7 | at Tulsa | L 40–43 | 5 | 3 | 1.5 | 1.5 | 0 |
| Oct 22 | vs. Houston | W 38–16 | 5 | 5 | 3 | 3 | 0 |
| Oct 29 | at Tulane | W 35–31 | 1 | 1 | 0 | 0 | 0 |
| Nov 5 | vs. Memphis | L 7–51 | 1 | 1 | 1 | 0 | 0 |
| Nov 12 | at East Carolina | W 55–31 | 1 | 1 | 0 | 0 | 0 |
| Nov 19 | vs. South Florida | L 27–35 | 1 | 1 | 0 | 0 | 0 |
| Nov 26 | vs. Navy | L 31–75 | 3 | 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.