Running back, Campbell, 2024–⁠26

J.J. Cowan

Number
No. 5
Height
5′11″
Weight
215 lb
Class (2026)
Junior
Hometown
Erwin, NC

J.J. Cowan plays running back for Campbell. Last time out, against Towson: 13 carries, 24 yards; 2 catches, 26 yards. Cowan leads Campbell in rushing yards this season.

2026 so far

471 rushing yards, 3 TD

Last game: 13 carries, 24 yards; 2 catches, 26 yards vs. Towson, W 24–⁠20

Next game: at Maine, Oct 24

Game by game this season, rushing yards
  1. 16@ETSU
  2. 83WCU
  3. 29@FLA
  4. 134NCAT
  5. 46@HAMP
  6. 139@NCCU
  7. 24TOW

Filled bars: wins; outlined: losses.

Career highs

142rushing yards, career highat Hampton, 20253rushing touchdowns, career highat Hampton, 20256catches, career highat William & Mary, 2024

Rushing

Rushing yards, season by season, with his team’s record

* The season in progress, so far.

SeasonTeamCarYdsAvgTDLong
2024Campbell703655.2147
2025Campbell1015445.4864
2026Campbell754716.3390
Career2461,3805.61290

Receiving

SeasonTeamRecYdsAvgTDLong
2024Campbell11777.0119
2025Campbell9535.9114
2026Campbell1113111.9135
Career312618.4335

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2024Campbell5RBFr.
2025Campbell5RBSo.
2026Campbell5RBJr.5′11″215

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/playPctileMedianTotalUsage
2025Campbell (FCS)1070.1976th (n=576)0.1020.316%
2026Campbell (FCS)840.1970th (n=478)0.1016.217%

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

2026 Campbell 7 games, 471 rushing yards, 3 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Aug 29atEast Tennessee StateW 49–⁠376160–––
Sep 6vs.Western CarolinaW 28–⁠19118303170
Sep 12atFloridaL 3–⁠5272901−20
Sep 19vs.North Carolina A&TW 42–⁠141113422511
Sep 26atHamptonW 44–⁠20134602140
Oct 3atNorth Carolina CentralW 38–⁠311413911250
Oct 17vs.TowsonW 24–⁠20132402260
2025 Campbell 10 games, 544 rushing yards, 8 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Aug 29atRhode IslandL 20–⁠317430111
Sep 6atEast CarolinaL 3–⁠565190220
Sep 13vs.FurmanL 24–⁠2815532160
Sep 20vs.BryantW 50–⁠4883902150
Sep 27vs.Western CarolinaL 35–⁠42490–––
Oct 4atNC StateL 10–⁠5612480–––
Oct 11atHamptonW 38–⁠211614231140
Oct 18vs.New HampshireL 10–⁠2413541–––
Oct 25atNorth Carolina A&TL 24–⁠289300–––
Nov 8vs.William & MaryL 27–⁠301210722150
2024 Campbell 9 games, 365 rushing yards, 1 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 21vs.Stony BrookL 17–⁠244260–––
Sep 28vs.Delaware StateW 44–⁠4112421–––
Oct 5vs.North Carolina CentralL 14–⁠4511470–––
Oct 19atWilliam & MaryL 28–⁠3563406441
Oct 26vs.North Carolina A&TW 21–⁠711740–––
Nov 2atElonL 27–⁠5083802170
Nov 9vs.RichmondL 24–⁠2712820–––
Nov 16atDelawareL 22–⁠4152003160
Nov 23vs.TowsonL 23–⁠45120–––

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.