Defensive line, East Carolina, 2024–26
Torin Brazell
- Number
- No. 98
- Height
- 6′2″
- Weight
- 278 lb
- Class (2026)
- Junior
- Hometown
- Starke, FL
Torin Brazell plays defensive line for East Carolina. Last time out, at UAB: 2 tackles.
2026 so far
12 tackles, 1 sack
Last game: 2 tackles at UAB, L 17–30
Next game: at Memphis, Oct 22
Filled bars: wins; outlined: losses.
Defense
* The season in progress, so far.
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2025 | East Carolina | 4 | 4 | 2 | 0 | 0 | 1 |
| 2026 | East Carolina | 12 | 3 | 2.5 | 1 | 0 | 3 |
| Career | 16 | 7 | 4.5 | 1 | 0 | 4 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2024 | East Carolina | 98 | DL | Fr. | ||
| 2025 | East Carolina | 98 | DL | So. | ||
| 2026 | East Carolina | 98 | DL | Jr. | 6′2″ | 278 |
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
2026 East Carolina 5 games, 12 tackles, 1 sack
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 5 | at Alabama | L 10–48 | 3 | 1 | 1 | 1 | 0 |
| Sep 12 | vs. App State | L 24–27 | 2 | 0 | 0 | 0 | 0 |
| Sep 19 | at Old Dominion | W 20–17 | 4 | 0 | 1 | 0 | 0 |
| Oct 10 | vs. Rice | W 28–12 | 1 | 1 | 0 | 0 | 0 |
| Oct 15 | at UAB | L 17–30 | 2 | 1 | 0.5 | 0 | 0 |
2025 East Carolina 3 games, 4 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 20 | vs. BYU | L 13–34 | 1 | 1 | 0 | 0 | 0 |
| Nov 8 | vs. Charlotte | W 48–22 | 1 | 1 | 0 | 0 | 0 |
| Nov 29 | at Florida Atlantic | W 42–3 | 2 | 2 | 2 | 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.