Defensive line, Louisville, 2025–26
Eric Hazzard
- Number
- No. 40
- Height
- 6′3″
- Weight
- 255 lb
- Class (2026)
- Freshman
- Hometown
- Franklin, TN
Eric Hazzard plays defensive line for Louisville. Last time out, against Florida State: 1 tackles.
2026 so far
5 tackles
Last game: 1 tackles vs. Florida State, W 44–20
Next game: vs. Stanford, Oct 31
Filled bars: wins; outlined: losses.
Defense
* The season in progress, so far.
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2025 | Louisville | 5 | 3 | 0 | 0 | 0 | 0 |
| 2026 | Louisville | 5 | 3 | 0 | 0 | 0 | 0 |
| Career | 10 | 6 | 0 | 0 | 0 | 0 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2025 | Louisville | 40 | DL | Yr 1 | ||
| 2026 | Louisville | 40 | DL | Fr. (Yr 2) | 6′3″ | 255 |
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 Louisville 4 games, 5 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 6 | vs. Ole Miss | L 38–41 | 1 | 0 | 0 | 0 | 0 |
| Sep 11 | vs. Villanova | W 59–13 | 2 | 1 | 0 | 0 | 0 |
| Sep 26 | vs. Wake Forest | L 27–30 | 1 | 1 | 0 | 0 | 0 |
| Oct 9 | vs. Florida State | W 44–20 | 1 | 1 | 0 | 0 | 0 |
2025 Louisville 4 games, 5 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Aug 30 | vs. Eastern Kentucky | W 51–17 | 2 | 2 | 0 | 0 | 0 |
| Nov 22 | at SMU | L 6–38 | 1 | 1 | 0 | 0 | 0 |
| Nov 29 | vs. Kentucky | W 41–0 | 1 | 0 | 0 | 0 | 0 |
| Dec 23 ✦ | vs. Toledo | W 27–22 | 1 | 0 | 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.