Running back, Utah, 2025–26
Daniel Bray
- Number
- No. 5
- Height
- 5′10″
- Weight
- 180 lb
- Class (2026)
- Sophomore
- Hometown
- Fort Worth, TX
Daniel Bray plays running back for Utah. Last time out, at Colorado: 1 catch, 15 yards.
2026 so far
129 rushing yards, 1 TD
Last game: 1 catch, 15 yards at Colorado, W 27–24
Next game: vs. Houston, Oct 24
Filled bars: wins; outlined: losses.
Career highs
121rushing yards, career highat BYU, 2025Rushing
* The season in progress, so far.
Receiving
Returns
Season lines from CollegeFootballData, regular season and bowls.
On the roster
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
| Season | Team | Plays | EPA/play | Pctile | Median | Total | Usage | Adj. rush |
|---|---|---|---|---|---|---|---|---|
| 2025 | Utah | 48 | 0.20 | – | – | 9.7 | 8% | 0.18 |
| 2026 | Utah | 32 | 0.13 | – | – | 4.3 | 7% | – |
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
| Season | Team | Success | Line yards | Second level | Open field | Stuffed |
|---|---|---|---|---|---|---|
| 2025 | Utah | 67% | 4.70 | 2.70 | 4.30 | 17% |
| 2026 | Utah | 35% | 2.80 | 1.00 | 2.90 | 30% |
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 Utah 6 games, 129 rushing yards, 1 TD
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Sep 3 | vs. Idaho | W 66–14 | 2 | 13 | 0 | – | – | – |
| Sep 12 | vs. Arkansas | W 43–10 | 4 | −1 | 0 | 2 | 14 | 0 |
| Sep 19 | vs. Utah State | W 33–0 | 3 | 82 | 1 | 4 | 19 | 0 |
| Sep 26 | at Iowa State | W 31–17 | 4 | 6 | 0 | 3 | 24 | 0 |
| Oct 10 | vs. Kansas | W 41–24 | 4 | 16 | 0 | 2 | 2 | 0 |
| Oct 17 | at Colorado | W 27–24 | 4 | 13 | 0 | 1 | 15 | 0 |
2025 Utah 9 games, 272 rushing yards, 1 TD
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Sep 27 | at West Virginia | W 48–14 | 3 | 32 | 0 | 1 | 2 | 0 |
| Oct 11 | vs. Arizona State | W 42–10 | 5 | 41 | 0 | 1 | 3 | 0 |
| Oct 18 | at BYU | L 21–24 | 10 | 121 | 1 | – | – | – |
| Oct 25 | vs.Colorado | W 53–7 | 4 | 9 | 0 | 1 | 11 | 0 |
| Nov 1 | vs. Cincinnati | W 45–14 | 9 | 43 | 0 | 3 | 41 | 0 |
| Nov 15 | at Baylor | W 55–28 | 4 | 10 | 0 | – | – | – |
| Nov 22 | vs. Kansas State | W 51–47 | 3 | 9 | 0 | 1 | 5 | 0 |
| Nov 28 | atKansas | W 31–21 | 1 | 4 | 0 | 1 | 5 | 0 |
| Dec 31 ✦ | vs. Nebraska | W 44–22 | 1 | 3 | 0 | – | – | – |
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.