Receiver, Arizona, 2014–17
Cam Denson
Lettered 2014–16 (school media guide)
- Number
- No. 3
- Height
- 5′11″
- Weight
- 187 lb
- Hometown
- Tuscon, AZ
Cam Denson played receiver at Arizona (2014–17).
Receiving
Defense
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.
Defense before 2016
| Season | G | Solo | Ast | Tkl |
|---|---|---|---|---|
| 2015 | 9 of 13 | 22 | 3 | 25 |
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.
Per play
| Season | Team | Plays | EPA/play | Pctile | Median | Total | Usage |
|---|---|---|---|---|---|---|---|
| 2016 | Arizona | 21 | 0.44 | – | – | 9.3 | 5% |
| 2017 | Arizona | 1 | 0.06 | – | – | 0.1 | – |
Expected points added: how much the player’s plays moved the team’s expected score, per play and in total. Plays: total EPA divided by EPA per play, the plays the source credits to him (for a receiver roughly his catches and runs, not every target; for a passer, not every attempt), so it can differ from attempts plus carries. Percentile: against the position’s regulars that season across all divisions on file (quarterbacks with 150+ plays, backs 60+, receivers and tight ends 30+), with how many there were (n) and their median; a dash means too few plays to rank. A season in progress uses the full-season bar scaled by games played, never below 75 plays for quarterbacks, 30 for backs and 20 for receivers. The cohort grows or shrinks with the source’s coverage each season (2025 lists far more players), so compare percentiles rather than raw EPA across years. FCS seasons are marked. Usage: the share of the team’s plays the player was part of (shown from 20 plays). From CollegeFootballData, 2013 on.
Game by game
2017 Arizona 1 game, 1 catch, 5 yards
| Date | Opponent | Result | Rec | Rec yds | Rec TD | Tkl | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|---|
| Sep 9 | vs. Houston | L 16–19 | 1 | 5 | 0 | – | – | – | – |
2016 Arizona 9 games, 15 catches, 242 yards, 2 TD
| Date | Opponent | Result | Rec | Rec yds | Rec TD | Tkl | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|---|
| Sep 10 | vs. Grambling | W 31–21 | 2 | 19 | 0 | – | – | – | – |
| Sep 24 | vs. Washington | L 28–35 | – | – | – | 1 | 0 | 0 | 0 |
| Oct 1 | at UCLA | L 24–45 | 2 | 16 | 1 | – | – | – | – |
| Oct 8 | at Utah | L 23–36 | – | – | – | 1 | 0 | 0 | 0 |
| Oct 15 | vs. USC | L 14–48 | 1 | 51 | 0 | – | – | – | – |
| Oct 29 | vs. Stanford | L 10–34 | 1 | 5 | 0 | – | – | – | – |
| Nov 5 | at Washington State | L 7–69 | 4 | 77 | 1 | – | – | – | – |
| Nov 12 | vs. Colorado | L 24–49 | 3 | 33 | 0 | – | – | – | – |
| Nov 19 | at Oregon State | L 17–42 | 2 | 41 | 0 | – | – | – | – |
2015 Arizona 3 games, 3 INT
| Date | Opponent | Result | Rec | Rec yds | Rec TD | Tkl | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|---|
| Sep 19 | vs. Northern Arizona | W 77–13 | – | – | – | – | – | 1 | – |
| Nov 21 | at Arizona State | L 37–52 | – | – | – | – | – | 1 | – |
| Dec 19 ✦ | vs. New Mexico | W 45–37 | – | – | – | – | – | 1 | – |
2014 Arizona 2 games, 2 INT
| Date | Opponent | Result | Rec | Rec yds | Rec TD | Tkl | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|---|
| Oct 25 | atWashington State | W 59–37 | – | – | – | – | – | 1 | – |
| Dec 31 ✦ | vs. Boise State | L 30–38 | – | – | – | – | – | 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.