Running back, Rice, 2017–⁠22

Cameron Montgomery

Number
No. 1
Height
5′5″
Weight
160 lb
Class (2022)
Senior
Hometown
Stafford, TX

Cameron Montgomery played running back at Rice (2017–⁠22).

Career highs

99rushing yards, career highat USC, 20222rushing touchdowns, career highvs. Louisiana Tech, 2021

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2017Rice11726.5012
2019Rice9303.308
2021Rice442565.8270
2022Rice935616.0057
Career1579195.9270

Receiving

SeasonTeamRecYdsAvgTDLong
2019Rice284.008
2021Rice7405.7012
2022Rice8759.4035
Career171237.2035

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2017Rice1RBYr 1
2018Rice1RBYr 2
2019Rice1RBYr 3
2020Rice1RBYr 4
2021Rice1RBYr 5
2022Rice1RBSr. (Yr 6)5′5″160

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

SeasonTeamPlaysEPA/playPctileMedianTotalUsageAdj. rush
2017Rice110.23––2.5––
2019Rice12-0.57––-6.9––
2021Rice310.01––0.56%–
2022Rice1080.0319th (n=470)0.143.312%-0.02

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). Adjusted pass and rush: EPA per play adjusted for the defenses faced (CollegeFootballData’s WEPA). From CollegeFootballData, 2013 on.

Game by game

2022 Rice 13 games, 561 rushing yards
DateOpponentResultCarYdsTDLongRecRec yds
Sep 3atUSCL 14–⁠66699055––
Sep 10vs.McNeeseW 52–⁠104102111
Sep 17vs.LouisianaW 33–⁠21532013––
Sep 24atHoustonL 27–⁠344200710
Oct 1vs.UABW 28–⁠2453402116
Oct 15atFlorida AtlanticL 14–⁠1732501918
Oct 22atLouisiana TechW 42–⁠4114870451−1
Oct 29vs.CharlotteL 23–⁠56103508––
Nov 3vs.UTEPW 37–⁠30858034135
Nov 12atWestern KentuckyL 10–⁠451161013216
Nov 19vs.UTSAL 7–⁠415−302––
Nov 26atNorth TexasL 17–⁠211149010––
Dec 17 ✦vs.Southern MissL 24–⁠38763057––
2021 Rice 11 games, 256 rushing yards, 2 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 4atArkansasL 17–⁠381−200––
Sep 18atTexasL 0–⁠582120939
Sep 25vs.Texas SouthernW 48–⁠3452709112
Oct 2vs.Southern MissW 24–⁠194110910
Oct 16atUTSAL 0–⁠452−600––
Oct 23atUABW 30–⁠242603––
Oct 30vs.North TexasL 24–⁠302−101––
Nov 6atCharlotteL 24–⁠31––––18
Nov 13vs.Western KentuckyL 21–⁠42736019111
Nov 20atUTEPL 28–⁠38978043––
Nov 27vs.Louisiana TechW 35–⁠311095270––
2019 Rice 5 games, 30 rushing yards
DateOpponentResultCarYdsTDLongRecRec yds
Aug 30atArmyL 7–⁠141202––
Sep 6vs.Wake ForestL 21–⁠4161908––
Sep 14vs.TexasL 13–⁠48––––18
Sep 21vs.BaylorL 13–⁠21110110
Oct 5atUABL 20–⁠351808––
2017 Rice 8 games, 72 rushing yards
DateOpponentResultCarYdsTDLongRecRec yds
Aug 26vs.StanfordL 7–⁠621404––
Sep 9atUTEPW 31–⁠14111011––
Sep 16atHoustonL 3–⁠381707––
Oct 21atUTSAL 7–⁠201202––
Oct 28vs.Louisiana TechL 28–⁠42442012––
Nov 4atUABL 21–⁠521000––
Nov 18atOld DominionL 21–⁠241−400––
Nov 25vs.North TexasL 14–⁠30110010––

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.