Running back, Houston, 2024–⁠26

D.J. Butler

Number
No. 25
Height
6′0″
Weight
190 lb
Class (2026)
Junior
Hometown
Mobile, AL

D.J. Butler plays running back for Houston.

2026 so far

86 rushing yards, 1 TD

Last game: vs. Oklahoma State, W 35–⁠32

Next game: at Utah, Oct 24

Game by game this season, rushing yards
  1. 17ORST
  2. 55SOU
  3. 11@TTU
  4. 3@KSU

Filled bars: wins; outlined: losses.

Rushing

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

* The season in progress, so far.

SeasonTeamCarYdsAvgTDLong
2024Houston161026.4028
2025Houston683014.4015
2026Houston11867.8115
Career954895.1128

Receiving

SeasonTeamRecYdsAvgTDLong
2024Houston4369.0027
2025Houston8587.3012
2026Houston111.001
Career13957.3027

Returns

SeasonTeamKRYdsTD
2024Houston2290
2026Houston4890
Career61180

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2024Houston25RBFr.
2025Houston25RBSo.
2026Houston25RBJr.6′0″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
2024Houston200.14––2.85%–
2025Houston760.0227th (n=576)0.101.89%0.08
2026Houston120.35––4.2––

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
2025Houston47%3.401.000.308%

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 5 games, 86 rushing yards, 1 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 5vs.Oregon StateW 33–⁠202170–––
Sep 12vs.SouthernW 77–⁠66551110
Sep 18atTexas TechL 26–⁠282110–––
Oct 10atKansas StateW 35–⁠16130–––
Oct 17vs.Oklahoma StateW 35–⁠32––––––
2025 Houston 11 games, 301 rushing yards
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Aug 28vs.Stephen F. AustinW 27–⁠05290–––
Sep 6atRiceW 35–⁠94110–––
Sep 26atOregon StateW 27–⁠243170–––
Oct 11atOklahoma StateW 39–⁠175170190
Oct 18vs.ArizonaW 31–⁠28270–––
Oct 25atArizona StateW 24–⁠164190–––
Nov 1vs.West VirginiaL 35–⁠455250190
Nov 7atUCFW 30–⁠2714690280
Nov 22vs.TCUL 14–⁠1783302130
Nov 29atBaylorW 31–⁠24105301120
Dec 27 ✦vs.LSUW 38–⁠358210170
2024 Houston 7 games, 102 rushing yards
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 14vs.RiceW 33–⁠7140–––
Oct 4atTCUW 30–⁠19250–––
Oct 19vs.KansasL 14–⁠4232801270
Nov 2vs.Kansas StateW 24–⁠196410140
Nov 15atArizonaL 3–⁠27120160
Nov 23vs.BaylorL 10–⁠202401−10
Nov 30atBYUL 18–⁠301180–––

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.