Running back, Charlotte, 2017–⁠22

Calvin Camp

Number
No. 2
Height
5′8″
Weight
183 lb
Class (2022)
Senior
Hometown
Hickory, NC

Calvin Camp played running back at Charlotte (2017–⁠22).

Career highs

111rushing yards, career highvs. Louisiana Tech, 20223rushing touchdowns, career highvs. Louisiana Tech, 2022

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2018Charlotte36932.6013
2020Charlotte19864.5121
2021Charlotte1136355.6444
2022Charlotte201939.7444
Career1881,0075.4944

Returns

SeasonTeamKRYdsTD
2018Charlotte190
2020Charlotte71150
2021Charlotte61360
Career142600

Receiving

SeasonTeamRecYdsAvgTDLong
2018Charlotte44611.5019
2021Charlotte151308.7153
Career191769.3153

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2017Charlotte2RBYr 1
2018Charlotte2RBYr 2
2019Charlotte2RBYr 3
2020Charlotte2RBYr 4
2021Charlotte2RBYr 5
2022Charlotte2RBSr. (Yr 6)5′8″183

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
2018Charlotte42-0.08––-3.27%0.02
2020Charlotte19-0.16––-3.0––
2021Charlotte1120.1032nd (n=277)0.1611.515%0.13
2022Charlotte190.46––8.7––

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 Charlotte 3 games, 193 rushing yards, 4 TD
DateOpponentResultCarRush ydsRush TDKRYds
Aug 27atFlorida AtlanticL 13–⁠43120––
Oct 29atRiceW 56–⁠238801––
Nov 19vs.Louisiana TechW 26–⁠21111113––
2021 Charlotte 12 games, 635 rushing yards, 4 TD
DateOpponentResultCarRush ydsRush TDKRYds
Sep 3vs.DukeW 31–⁠289420––
Sep 11vs.Gardner-WebbW 38–⁠107651––
Sep 18atGeorgia StateL 9–⁠2013500139
Sep 24vs.Middle TennesseeW 42–⁠39121011112
Oct 2atIllinoisL 14–⁠247290––
Oct 8atFlorida InternationalW 45–⁠3312661122
Oct 21vs.Florida AtlanticL 9–⁠387380––
Oct 30atWestern KentuckyL 13–⁠457600––
Nov 6vs.RiceW 31–⁠246220––
Nov 13atLouisiana TechL 32–⁠429270––
Nov 20vs.MarshallL 28–⁠498450363
Nov 27atOld DominionL 34–⁠5616901––
2020 Charlotte 6 games, 7 returns, 115 yards
DateOpponentResultCarRush ydsRush TDKRYds
Sep 12atApp StateL 20–⁠35–––124
Oct 3atFlorida AtlanticL 17–⁠21200––
Oct 10atNorth TexasW 49–⁠214451229
Oct 24vs.UTEPW 38–⁠28650116
Oct 31atDukeL 19–⁠536340346
Dec 6vs.Western KentuckyL 19–⁠37120––
2018 Charlotte 9 games, 93 rushing yards
DateOpponentResultCarRush ydsRush TDKRYds
Sep 1vs.FordhamW 34–⁠104180––
Sep 8vs.App StateL 9–⁠456130––
Sep 22atMassachusettsL 31–⁠493180––
Sep 29atUABL 7–⁠28110––
Oct 13vs.Western KentuckyW 40–⁠1412380––
Oct 20atMiddle TennesseeL 13–⁠2135019
Oct 27vs.Southern MissW 20–⁠171−20––
Nov 3atTennesseeL 3–⁠142−50––
Nov 10atMarshallL 13–⁠30470––

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.