Defensive tackle, UConn (from Duke), 2023–26
Desmond Aladuge
Lettered 2024 at Duke (school media guide)
- Number
- No. 14
- Height
- 6′4″
- Weight
- 285 lb
- Class (2026)
- Sophomore
- Hometown
- Milford, DE
Desmond Aladuge plays defensive tackle for UConn, after Duke (2023–25). Last time out, against Syracuse: 1 tackles.
2026 so far
5 tackles
Last game: 1 tackles vs. Syracuse, L 41–42
Next game: vs. Massachusetts, Oct 23
Filled bars: wins; outlined: losses.
Team titles: ACC champions, 2025
Defense
* The season in progress, so far.
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2023 | Duke | 14 | DT | Yr 1 | ||
| 2024 | Duke | 14 | DT | Yr 2 | ||
| 2025 | Duke | 14 | DT | Yr 3 | ||
| 2026 | UConn | 14 | DT | So. (Yr 4) | 6′4″ | 285 |
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 UConn 4 games, 5 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 5 | vs. | W 56–7 | 1 | 0 | 0 | 0 | 0 |
| Sep 19 | at | W 48–20 | 1 | 0 | 0 | 0 | 0 |
| Sep 26 | at | L 21–24 | 2 | 2 | 0 | 0 | 0 |
| Oct 3 | vs. | L 41–42 | 1 | 1 | 1 | 0 | 0 |
2025 Duke 1 game, 1 tackle
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 27 | at | W 38–3 | 1 | 0 | 0 | 0 | 0 |
2024 Duke 4 games, 7 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Aug 30 | vs. | W 26–3 | 2 | 0 | 0.5 | 0 | 0 |
| Sep 6 | vs. | W 26–20 | 2 | 1 | 1 | 0 | 0 |
| Sep 14 | vs. | W 26–21 | 1 | 0 | 0 | 0 | 0 |
| Oct 5 | at | L 14–24 | 2 | 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.
