Safety, Southern Utah (from Sacramento State), 2022–25
Kameron Rocha
- Number
- No. 21
- Height
- 6′0″
- Weight
- 180 lb
- Class (2025)
- Senior
- Hometown
- San Jacinto, CA
Kameron Rocha played safety at Sacramento State (2022–23) and Southern Utah (2024–25).
Career highs
9tackles, career highat UTEP, 2024Team titles: Big Sky champions, 2022
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | Int | PD | Hur |
|---|---|---|---|---|---|---|---|---|
| 2023 | Sacramento State | 2 | 2 | 0 | 0 | 1 | 0 | 0 |
| 2024* | Southern Utah | 11 | 7 | 1 | 0 | 1 | 0 | 0 |
| Career | 13 | 9 | 1 | 0 | 2 | 0 | 0 | |
Season lines from CollegeFootballData, regular season and bowls. * That team-season’s player lines are missing part of the team’s yards in our source, so these numbers may be short.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2022 | Sacramento State | 21 | S | Fr. | ||
| 2023 | Sacramento State | 21 | S | So. | ||
| 2024 | Southern Utah | 21 | S | Jr. | ||
| 2025 | Southern Utah | 21 | S | Sr. | 6′0″ | 180 |
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
2024 Southern Utah 3 games, 11 tackles, 1 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Aug 29 | at Utah | L 0–49 | 2 | 0 | 0 | 0 | 0 | 0 |
| Sep 7 | at UTEP | W 27–24 | 9 | 7 | 1 | 0 | 0 | 0 |
| Nov 9 | at North Alabama | W 38–26 | – | – | – | – | 1 | – |
2023 Sacramento State 2 games, 2 tackles, 1 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 16 | at Stanford | W 30–23 | 2 | 2 | 0 | 0 | 0 | 0 |
| Sep 30 | vs. Northern Arizona | W 31–30 | – | – | – | – | 1 | – |
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.