Defensive line, BYU (from Navy), 2017–22
Pepe Tanuvasa
- Number
- No. 45
- Height
- 6′1″
- Weight
- 245 lb
- Class (2022)
- Senior
- Hometown
- Tigard, OR
Pepe Tanuvasa played defensive line at Navy (2017–18) and BYU (2019–22).
Career highs
11tackles, career highat Air Force, 2018Defense
Season lines from CollegeFootballData, regular season and bowls. A dash: the source has no number for that season (often an FCS season), and career totals count only the numbers on file.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2017 | Navy | 45 | DL | Yr 1 | ||
| 2018 | Navy | 45 | DL | Yr 2 | ||
| 2019 | BYU | 45 | DL | Yr 3 | ||
| 2020 | BYU | 45 | DL | Yr 4 | ||
| 2021 | BYU | 45 | DL | Yr 5 | ||
| 2022 | BYU | 45 | DL | Sr. (Yr 6) | 6′1″ | 245 |
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
2022 BYU 10 games, 35 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 10 | vs. Baylor | W 26–20 | 1 | 0 | 0 | 0 | 0 | 0 |
| Sep 17 | at Oregon | L 20–41 | 3 | 2 | 0 | 0 | 0 | 0 |
| Sep 24 | vs. Wyoming | W 38–24 | 2 | 1 | 0 | 0 | 0 | 1 |
| Oct 8 | vs. Notre Dame | L 20–28 | 4 | 1 | 0 | 0 | 0 | 0 |
| Oct 15 | vs. Arkansas | L 35–52 | 3 | 0 | 0 | 0 | 0 | 0 |
| Oct 22 | at Liberty | L 14–41 | 4 | 2 | 0 | 0 | 0 | 0 |
| Oct 28 | vs. East Carolina | L 24–27 | 6 | 1 | 0 | 0 | 0 | 0 |
| Nov 5 | at Boise State | W 31–28 | 3 | 1 | 0 | 0 | 0 | 1 |
| Nov 19 | vs. Utah Tech | W 52–26 | 7 | 4 | 0.5 | 0 | 0 | 0 |
| Nov 26 | at Stanford | W 35–26 | 2 | 1 | 0 | 0 | 0 | 0 |
2021 BYU 12 games, 42 tackles, 3 sacks, 1 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 4 | vs. Arizona | W 24–16 | 1 | 1 | 1 | 0 | 0 | 0 |
| Sep 11 | vs. Utah | W 26–17 | 1 | 1 | 0 | 0 | 0 | 0 |
| Sep 18 | vs. Arizona State | W 27–17 | 2 | 1 | 1 | 1 | 0 | 0 |
| Sep 25 | vs. South Florida | W 35–27 | 7 | 3 | 1 | 0 | 0 | 0 |
| Oct 1 | at Utah State | W 34–20 | 4 | 2 | 0 | 0 | 0 | 0 |
| Oct 9 | vs.Boise State | L 17–26 | 4 | 1 | 1 | 1 | 0 | 0 |
| Oct 16 | atBaylor | L 24–38 | 3 | 2 | 0 | 0 | 0 | 0 |
| Oct 23 | at Washington State | W 21–19 | 3 | 3 | 0 | 0 | 0 | 0 |
| Nov 6 | vs. Idaho State | W 59–14 | 3 | 1 | 1 | 1 | 1 | 0 |
| Nov 20 | at Georgia Southern | W 34–17 | 6 | 4 | 0.5 | 0 | 0 | 0 |
| Nov 27 | at USC | W 35–31 | 3 | 1 | 0 | 0 | 0 | 0 |
| Dec 18 ✦ | vs. UAB | L 28–31 | 5 | 3 | 1.5 | 0 | 0 | 0 |
2020 BYU 9 games, 24 tackles, 1 sack, 1 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 7 | at Navy | W 55–3 | 8 | 4 | 0 | 0 | 0 | 0 |
| Sep 26 | vs. Troy | W 48–7 | 0 | 0 | 0 | 0 | 0 | 2 |
| Oct 2 | vs. Louisiana Tech | W 45–14 | 2 | 1 | 0 | 0 | 0 | 0 |
| Oct 24 | vs. Texas State | W 52–14 | 2 | 0 | 0 | 0 | 1 | 0 |
| Oct 31 | vs. Western Kentucky | W 41–10 | 2 | 2 | 0 | 0 | 0 | 0 |
| Nov 21 | vs. North Alabama | W 66–14 | 4 | 1 | 0 | 0 | 0 | 0 |
| Dec 5 | at Coastal Carolina | L 17–22 | 2 | 1 | 1 | 1 | 0 | 0 |
| Dec 12 | vs. San Diego State | W 28–14 | 3 | 2 | 0 | 0 | 0 | 0 |
| Dec 22 ✦ | vs. UCF | W 49–23 | 1 | 1 | 0 | 0 | 0 | 1 |
2018 Navy 8 games, 32 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 1 | at Hawai’i | L 41–59 | 3 | 2 | 0 | 0 | 0 | 0 |
| Sep 15 | vs. Lehigh | W 51–21 | 4 | 2 | 0 | 0 | 0 | 0 |
| Oct 6 | at Air Force | L 7–35 | 11 | 5 | 0 | 0 | 0 | 0 |
| Oct 20 | vs. Houston | L 36–49 | 1 | 0 | 0 | 0 | 0 | 0 |
| Oct 27 | vs.Notre Dame | L 22–44 | 3 | 2 | 0 | 0 | 0 | 0 |
| Nov 3 | at Cincinnati | L 0–42 | 3 | 0 | 0 | 0 | 0 | 0 |
| Nov 24 | at Tulane | L 28–29 | 6 | 4 | 0 | 0 | 0 | 0 |
| Dec 8 | vs. Army | L 10–17 | 1 | 0 | 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.