Defensive line, Bowling Green, 2017–20
Demontae Haigler
Lettered 2018–19 (school media guide)
- Number
- No. 35
- Height
- 6′1″
- Weight
- 295 lb
- Class (2020)
- Senior
- Hometown
- Montgomery, AL
Demontae Haigler played defensive line at Bowling Green (2017–20).
Career highs
2sacks, career highvs. Kent State, 2018Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2018 | Bowling Green | 13 | 9 | 4 | 3 | 0 | 1 |
| 2019 | Bowling Green | 6 | 4 | 1 | 1 | 0 | 0 |
| Career | 19 | 13 | 5 | 4 | 0 | 1 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2017 | Bowling Green | 35 | DL | Fr. | ||
| 2018 | Bowling Green | 35 | DL | So. | ||
| 2019 | Bowling Green | 35 | DL | Jr. | ||
| 2020 | Bowling Green | 35 | DL | Sr. | 6′1″ | 295 |
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 Bowling Green 5 games, 6 tackles, 1 sack
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Aug 29 | vs. | W 46–3 | 2 | 1 | 0 | 0 | 0 |
| Sep 14 | vs. | L 7–35 | 1 | 1 | 1 | 1 | 0 |
| Sep 21 | at | L 20–62 | 1 | 0 | 0 | 0 | 0 |
| Oct 12 | vs. | W 20–7 | 1 | 1 | 0 | 0 | 0 |
| Oct 26 | at | L 10–49 | 1 | 1 | 0 | 0 | 0 |
2018 Bowling Green 6 games, 13 tackles, 3 sacks
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 15 | vs. | W 42–35 | 1 | 1 | 1 | 1 | 0 |
| Sep 22 | vs. | L 23–38 | 2 | 2 | 1 | 0 | 0 |
| Oct 6 | at | L 36–52 | 1 | 0 | 0 | 0 | 0 |
| Oct 13 | vs. | L 35–42 | 3 | 1 | 0 | 0 | 0 |
| Oct 20 | at | L 14–49 | 2 | 1 | 0 | 0 | 0 |
| Oct 30 | vs. | L 28–35 | 4 | 4 | 2 | 2 | 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.
