Defensive back, Northern Colorado (from Wyoming), 2019–⁠23

Cameron Murray

Number
No. 5
Height
6′1″
Weight
180 lb
Class (2023)
Senior
Hometown
Aurora, CO

Cameron Murray played defensive back at Wyoming (2019–⁠21) and Northern Colorado (2022–⁠23).

Defense

Tackles, season by season, with his team’s record
SeasonTeamTklSoloTFLSacksIntPDHur
2019Wyoming3100000
2020Wyoming6400000
2021Wyoming1000000
2022Northern Colorado7700010
2023Northern Colorado7310200
Career241510210

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

SeasonTeamNo.PosClassHtWt
2019Wyoming5DBYr 1
2020Wyoming5DBYr 2
2021Wyoming5DBYr 3
2022Northern Colorado5DBYr 4
2023Northern Colorado5DBSr. (Yr 5)6′1″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

2023 Northern Colorado 3 games, 7 tackles, 2 INT
DateOpponentResultTklSoloTFLSacksIntPD
Sep 16atWashington StateL 21–⁠64731000
Sep 30vs.Weber StateL 21–⁠28––––1–
Nov 18vs.Portland StateL 23–⁠27––––1–
2022 Northern Colorado 2 games, 7 tackles
DateOpponentResultTklSoloTFLSacksIntPD
Sep 3vs.Houston ChristianL 34–⁠46––––––
Sep 10atWyomingL 10–⁠33770001
2021 Wyoming 1 game, 1 tackle
DateOpponentResultTklSoloTFLSacksIntPD
Sep 11atNorthern IllinoisW 50–⁠43100000
2020 Wyoming 3 games, 6 tackles
DateOpponentResultTklSoloTFLSacksIntPD
Oct 24atNevadaL 34–⁠37110000
Oct 30vs.Hawai’iW 31–⁠7320000
Dec 5atNew MexicoL 16–⁠17210000
2019 Wyoming 3 games, 3 tackles
DateOpponentResultTklSoloTFLSacksIntPD
Sep 28vs.UNLVW 53–⁠17110000
Oct 19vs.New MexicoW 23–⁠10100000
Nov 16atUtah StateL 21–⁠26100000

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.