Running back, UT Rio Grande Valley (from Yale), 2021–⁠25

Nathan Denney

Number
No. 21
Height
5′9″
Weight
206 lb
Class (2025)
Sophomore
Hometown
Georgetown, TX

Nathan Denney played running back at Yale (2021–⁠24) and UT Rio Grande Valley (2025).

Career highs

158rushing yards, career highvs. East Texas A&M, 20252rushing touchdowns, career hightwice; last vs. Nicholls, 2025

Team titles: Ivy League champions, 2022 and 2023

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2022Yale20482.4134
2023Yale13695.3214
2024Yale662023.1212
2025UT Rio Grande Valley1416614.7442
Career2409804.1942

Receiving

SeasonTeamRecYdsAvgTDLong
2022Yale188.008
2024Yale10999.9124
2025UT Rio Grande Valley2525310.1142
Career3636010.0242

Returns

SeasonTeamKRYdsTD
2022Yale1100
2023Yale3410
2024Yale4810
Career81320

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2022Yale21RBYr 1
2023Yale21RBYr 2
2024Yale21RBYr 3
2025UT Rio Grande Valley21RBSo. (Yr 4)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
2022Yale (FCS)12-0.23––-2.7–
2023Yale (FCS)80.36––2.8–
2024Yale (FCS)71-0.039th (n=434)0.16-1.812%
2025UT Rio Grande Valley (FCS)1400.1050th (n=576)0.1014.429%

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 UT Rio Grande Valley 9 games, 661 rushing yards, 4 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Aug 30vs.Sul Ross StateW 66–⁠03902240
Sep 6atPrairie View A&MW 27–⁠212310115370
Sep 27atSE LouisianaL 31–⁠457560–––
Oct 18atLamarL 21–⁠23197512210
Oct 25vs.Incarnate WordW 56–⁠28136404451
Nov 1atStephen F. AustinL 17–⁠41112103170
Nov 8vs.NichollsW 28–⁠212512023500
Nov 15atMcNeeseW 28–⁠13145705520
Nov 22vs.East Texas A&MW 33–⁠14261580170
2024 Yale 9 games, 202 rushing yards, 2 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 21atHoly CrossW 38–⁠31298023250
Sep 28atCornellL 23–⁠47103603240
Oct 5vs.Central ConnecticutW 23–⁠223140–––
Oct 12vs.DartmouthL 43–⁠443−10–––
Oct 19vs.LehighW 38–⁠238460100
Oct 25atPennsylvaniaW 31–⁠104100–––
Nov 1atColumbiaL 10–⁠131201241
Nov 9vs.BrownW 56–⁠346502260
Nov 16vs.PrincetonW 42–⁠282100–––
2023 Yale 6 games, 69 rushing yards, 2 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 16vs.Holy CrossL 24–⁠49330–––
Sep 23vs.CornellL 21–⁠23130–––
Sep 30vs.Morgan StateW 45–⁠33220–––
Oct 14vs.Sacred HeartW 31–⁠3––––––
Oct 28vs.ColumbiaW 35–⁠72231–––
Nov 18vs.HarvardW 23–⁠184181–––
2022 Yale 6 games, 48 rushing yards, 1 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 17atHoly CrossL 14–⁠385181180
Sep 24atCornellW 38–⁠14440–––
Oct 15vs.BucknellW 29–⁠92120–––
Oct 22atPennsylvaniaL 13–⁠20––––––
Oct 28atColumbiaW 41–⁠16210–––
Nov 5vs.BrownW 69–⁠177130–––

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.