Defensive back, Northern Iowa (from Grambling), 2018–22
Damien Crumitie
- Number
- No. 38
- Height
- 5′11″
- Weight
- 190 lb
- Class (2022)
- Senior
- Hometown
- Tallahassee, FL
Damien Crumitie played defensive back at Grambling (2018–19) and Northern Iowa (2022).
Career highs
8tackles, career highat Louisiana Tech, 2019Defense
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2018 | Grambling | 38 | DB | Yr 1 | ||
| 2019 | Grambling | 38 | DB | Yr 2 | ||
| 2022 | Northern Iowa | 38 | DB | Sr. (Yr 5) | 5′11″ | 190 |
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
2019 Grambling 2 games, 9 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Aug 31 | at UL Monroe | L 9–31 | 1 | 1 | 0 | 0 | 0 |
| Sep 7 | at Louisiana Tech | L 14–20 | 8 | 5 | 0 | 0 | 0 |
No box score in the source for Sep 21 at Alabama State; Sep 28 at Prairie View A&M; Oct 5 at Jackson State; Oct 12 vs. Alabama A&M; Oct 26 at Arkansas–Pine Bluff; Nov 2 vs. Texas Southern; Nov 9 vs. Alcorn State; Nov 16 at Mississippi Valley State; Nov 30 vs. Southern, so those games are not listed.
2018 Grambling 1 game, 1 tackle
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 1 | at Louisiana | L 17–49 | 1 | 1 | 0 | 0 | 1 |
No box score in the source for Sep 8 at Northwestern State; Sep 22 vs. Alabama State; Sep 29 vs. Prairie View A&M; Oct 6 vs. Oklahoma Panhandle; Oct 13 at Texas Southern; Oct 20 at Alcorn State; Oct 27 vs. Arkansas–Pine Bluff; Nov 3 vs. Mississippi Valley State; Nov 10 at Alabama A&M; Nov 24 at Southern, so those games are not listed.
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.