Defensive back, Miami (from USC, Utah), 2019–25
Briton Allen
- Number
- No. 40
- Height
- 6′0″
- Weight
- 190 lb
- Class (2025)
- Senior
- Hometown
- Orlando, FL
Briton Allen played defensive back at USC (2019–22), Utah (2023) and Miami (2025).
Defense
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2019 | USC | 40 | DB | Yr 1 | ||
| 2020 | USC | 40 | DB | Yr 2 | ||
| 2021 | USC | 40 | DB | Yr 3 | ||
| 2022 | USC | 40 | DB | Yr 4 | ||
| 2023 | Utah | 40 | DB | Yr 5 | ||
| 2025 | Miami | 40 | DB | Sr. (Yr 7) | 6′0″ | 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
2023 Utah 3 games, 6 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Aug 31 | vs. Florida | W 24–11 | 1 | 0 | 0 | 0 | 0 |
| Oct 14 | vs. California | W 34–14 | 2 | 1 | 0 | 0 | 0 |
| Oct 21 | at USC | W 34–32 | 3 | 3 | 0 | 0 | 0 |
2020 USC 2 games, 3 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Nov 14 | at Arizona | W 34–30 | 1 | 1 | 0 | 0 | 0 |
| Dec 6 | vs. Washington State | W 38–13 | 2 | 2 | 0 | 0 | 0 |
2019 USC 6 games, 6 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Aug 31 | vs. Fresno State | W 31–23 | 1 | 0 | 0 | 0 | 0 |
| Sep 7 | vs. Stanford | W 45–20 | 1 | 0 | 0 | 0 | 0 |
| Nov 2 | vs. Oregon | L 24–56 | 1 | 0 | 0 | 0 | 0 |
| Nov 9 | at Arizona State | W 31–26 | 1 | 1 | 0 | 0 | 0 |
| Nov 16 | atCalifornia | W 41–17 | 1 | 1 | 0 | 0 | 0 |
| Nov 23 | vs. UCLA | W 52–35 | 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.