Running back, Houston, 2023–⁠26

Re’Shaun Sanford II

Number
No. 6
Height
5′9″
Weight
190 lb
Class (2026)
Junior
Hometown
Harker Heights, TX

Re’Shaun Sanford II plays running back for Houston. Last time out, against Oklahoma State: 9 carries, 36 yards; 1 catch, 10 yards.

2026 so far

440 rushing yards, 2 TD

Last game: 9 carries, 36 yards; 1 catch, 10 yards vs. Oklahoma State, W 35–⁠32

Next game: at Utah, Oct 24

Game by game this season, rushing yards
  1. 75ORST
  2. 27SOU
  3. 30@TTU
  4. 120@GASO
  5. 62UCF
  6. 90@KSU
  7. 36OKST

Filled bars: wins; outlined: losses.

Career highs

120rushing yards, career highat Georgia Southern, 2026

Rushing

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

* The season in progress, so far.

SeasonTeamCarYdsAvgTDLong
2024Houston944444.7138
2026Houston844405.2256
Career1788845.0356

Receiving

SeasonTeamRecYdsAvgTDLong
2024Houston181578.7019
2026Houston1012612.6027
Career2828310.1027

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2023Houston6RBRS
2024Houston6RBFr.
2025Houston6RBSo.
2026Houston6RBJr.5′9″190

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
2024Houston1080.0112th (n=434)0.161.115%0.05
2026Houston940.1355th (n=478)0.1012.019%0.17

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.

Rushing detail

SeasonTeamSuccessLine yardsSecond levelOpen fieldStuffed
2026Houston39%3.601.100.8012%

Where his yards came from, per carry: line yards are the ones credited to the blockers (the first few, and losses), second level the yards 5 to 10 past the line, open field those beyond 10. Success: carries that kept the offense on schedule. Stuffed: carries stopped at or behind the line. From CollegeFootballData, FBS games, 2025 on.

Game by game

2026 Houston 7 games, 440 rushing yards, 2 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 5vs.Oregon StateW 33–⁠2011751190
Sep 12vs.SouthernW 77–⁠642711270
Sep 18atTexas TechL 26–⁠2853005500
Sep 26atGeorgia SouthernW 42–⁠28171200–––
Oct 3vs.UCFW 27–⁠17186202300
Oct 10atKansas StateW 35–⁠1620900–––
Oct 17vs.Oklahoma StateW 35–⁠3293601100
2024 Houston 12 games, 444 rushing yards, 1 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Aug 31vs.UNLVL 7–⁠2741303250
Sep 7atOklahomaL 12–⁠1672003480
Sep 14vs.RiceW 33–⁠715710–––
Sep 21atCincinnatiL 0–⁠3466202230
Sep 28vs.Iowa StateL 0–⁠20240–––
Oct 4atTCUW 30–⁠196381–––
Oct 19vs.KansasL 14–⁠4231401−50
Oct 26vs.UtahW 17–⁠1416720–––
Nov 2vs.Kansas StateW 24–⁠19660160
Nov 15atArizonaL 3–⁠27107605400
Nov 23vs.BaylorL 10–⁠2083702160
Nov 30atBYUL 18–⁠3011310140

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.