Running back, Western Kentucky (from Virginia Tech, Elon), 2020–⁠25

Jalen Hampton

Number
No. 23
Height
5′9″
Weight
206 lb
Class (2025)
Senior
Hometown
Rockville, MD

Jalen Hampton played running back at Virginia Tech (2020–⁠21), Elon (2022–⁠23) and Western Kentucky (2024–⁠25).

Career highs

177rushing yards, career highat Hampton, 20224rushing touchdowns, career highat Campbell, 2023

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2022Elon2311,0624.61049
2023Elon1848734.7649
2024Western Kentucky11575.2014
2025Western Kentucky11272.507
Career4372,0194.61649

Receiving

SeasonTeamRecYdsAvgTDLong
2022Elon8303.8010
2023Elon9414.6014
Career17714.2014

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2020Virginia Tech23RB
2021Virginia Tech23RBRS
2022Elon23RBFr.
2023Elon23RBSo.
2024Western Kentucky23RBJr.
2025Western Kentucky23RBSr.5′9″206

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
2022Elon (FCS)196-0.039th (n=470)0.14-4.932%
2023Elon (FCS)–0.00––0.0–
2024Western Kentucky90.31––2.8–
2025Western Kentucky10-0.08––-0.8–

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

2025 Western Kentucky 3 games, 27 rushing yards
DateOpponentResultCarYdsTDLongRecRec yds
Aug 30vs.North AlabamaW 55–⁠661806––
Oct 3atDelawareW 27–⁠24––––––
Nov 1vs.New Mexico StateW 35–⁠165907––
2024 Western Kentucky 6 games, 57 rushing yards
DateOpponentResultCarYdsTDLongRecRec yds
Sep 7vs.Eastern KentuckyW 31–⁠01303––
Sep 14atMiddle TennesseeW 49–⁠21525014––
Sep 28atBoston CollegeL 20–⁠211808––
Nov 9atNew Mexico StateW 41–⁠281−100––
Nov 23atLibertyL 21–⁠38220011––
Nov 30vs.Jacksonville StateW 19–⁠171202––
2023 Elon 11 games, 873 rushing yards, 6 TD
DateOpponentResultCarYdsTDLongRecRec yds
Aug 31atWake ForestL 17–⁠371589149211
Sep 9atGardner-WebbL 27–⁠34187701725
Sep 16vs.North Carolina A&TW 27–⁠316153045114
Sep 23atCampbellW 28–⁠242916242210
Sep 30vs.William & MaryW 14–⁠61374015––
Oct 7vs.North Carolina CentralL 23–⁠34101309––
Oct 14atVillanovaL 0–⁠21101909––
Oct 21vs.MonmouthW 28–⁠26228001512
Nov 4atDelawareW 33–⁠272646013112
Nov 11atRichmondL 24–⁠3814941421−3
Nov 18vs.HamptonW 51–⁠141166023––
2022 Elon 11 games, 1,062 rushing yards, 10 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 3atVanderbiltL 31–⁠4212190511
Sep 17vs.Gardner-WebbW 30–⁠2434168022110
Sep 24atWilliam & MaryW 35–⁠312814532239
Oct 1vs.RichmondW 30–⁠271593148––
Oct 8vs.TowsonW 27–⁠102448011––
Oct 15atRhode IslandL 10–⁠172081123––
Oct 22atNew HampshireL 22–⁠401784022––
Oct 29vs.DelawareW 27–⁠732136017––
Nov 5vs.UAlbanyW 27–⁠31581218––
Nov 12atHamptonW 38–⁠2424177349––
Nov 26atFurmanL 6–⁠311030011310

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.