Defensive end, San José State, 2017–20
Cameron Alexander
- Number
- No. 95
- Height
- 6′5″
- Weight
- 300 lb
- Class (2020)
- Senior
- Hometown
- Los Angeles, CA
Cameron Alexander played defensive end at San José State (2017–20).
Team titles: Mountain West champions, 2020
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2017 | San José State | 5 | 2 | 0 | 0 | 0 | 0 |
| 2018 | San José State | 7 | 1 | 0.5 | 0 | 0 | 0 |
| 2019 | San José State | 5 | 3 | 0 | 0 | 0 | 0 |
| Career | 17 | 6 | 0.5 | 0 | 0 | 0 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2017 | San José State | 95 | DE | Fr. | ||
| 2018 | San José State | 95 | DE | So. | ||
| 2019 | San José State | 95 | DE | Jr. | ||
| 2020 | San José State | 95 | DE | Sr. | 6′5″ | 300 |
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
2019 San José State 3 games, 5 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 27 | at Air Force | L 24–41 | 3 | 2 | 0 | 0 | 0 |
| Nov 2 | vs. Boise State | L 42–52 | 1 | 0 | 0 | 0 | 0 |
| Nov 30 | vs. Fresno State | W 17–16 | 1 | 1 | 0 | 0 | 0 |
2018 San José State 5 games, 7 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 8 | at Washington State | L 0–31 | 1 | 0 | 0 | 0 | 0 |
| Sep 29 | vs. Hawai’i | L 41–44 | 2 | 1 | 0 | 0 | 0 |
| Oct 6 | vs. Colorado State | L 30–42 | 2 | 0 | 0.5 | 0 | 0 |
| Oct 13 | vs. Army | L 3–52 | 1 | 0 | 0 | 0 | 0 |
| Nov 3 | at Wyoming | L 9–24 | 1 | 0 | 0 | 0 | 0 |
2017 San José State 2 games, 5 tackles
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.