Linebacker, Nevada, 2012–16
Alex Bertrando
- Number
- No. 56
- Height
- 6′2″
- Hometown
- Loomis, CA
Alex Bertrando played linebacker at Nevada (2012–16).
Career highs
15tackles, career highvs. Utah State, 2016Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2016 | Nevada | 105 | 62 | 5.5 | 0 | 0 | 0 |
Season lines from CollegeFootballData, regular season and bowls.
Defense before 2016
| Season | G | Solo | Ast | Tkl |
|---|---|---|---|---|
| 2014 | 8 of 13 | 2 | 4 | 6 |
| 2015 | 10 of 13 | 14 | 8 | 22 |
Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources: ESPN play-by-play participants, via SportsDataverse: tackles only, counted in the games whose play-by-play names tacklers (G: those games, of his team’s), so part of the season, not its total. A dash: the source has no number for it.
On the roster
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
2016 Nevada 11 games, 105 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 2 | vs. Cal Poly | W 30–27 | 10 | 5 | 1 | 0 | 0 |
| Sep 10 | at Notre Dame | L 10–39 | 8 | 7 | 0 | 0 | 0 |
| Sep 17 | vs. Buffalo | W 38–14 | 10 | 5 | 0 | 0 | 0 |
| Sep 24 | at Purdue | L 14–24 | 10 | 8 | 1 | 0 | 0 |
| Oct 1 | at Hawai’i | L 17–38 | 4 | 4 | 0 | 0 | 0 |
| Oct 8 | vs. Fresno State | W 27–22 | 14 | 4 | 0 | 0 | 0 |
| Oct 15 | at San José State | L 10–14 | 10 | 2 | 1 | 0 | 0 |
| Nov 5 | at New Mexico | L 26–35 | 12 | 10 | 0 | 0 | 0 |
| Nov 12 | vs. San Diego State | L 16–46 | 5 | 3 | 0 | 0 | 0 |
| Nov 19 | vs. Utah State | W 38–37 | 15 | 10 | 2 | 0 | 0 |
| Nov 26 | at UNLV | W 45–10 | 7 | 4 | 0.5 | 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.