Running back, Michigan, 2023–⁠26

Bryson Kuzdzal

Number
No. 24
Height
5′11″
Weight
210 lb
Class (2026)
Senior
Hometown
Ada, MI

Bryson Kuzdzal plays running back for Michigan. Last time out, against Penn State: 2 carries, 38 yards, 1 TD; 1 tackles.

2026 so far

8 returns, 170 yards

Last game: 2 carries, 38 yards, 1 TD; 1 tackles vs. Penn State, W 21–⁠18

Next game: vs. Indiana, Oct 24

Game by game this season, rushing yards
  1. 12OU
  2. 14UTEP
  3. 5IOWA
  4. 38PSU

Filled bars: wins; outlined: losses.

Career highs

100rushing yards, career highat Maryland, 20253rushing touchdowns, career highat Maryland, 2025

Team titles: National champions, 2023; Big Ten champions, 2023

Rushing

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

* The season in progress, so far.

SeasonTeamCarYdsAvgTDLong
2025Michigan763264.3422
2026Michigan11696.3143
Career873954.5543

Returns

SeasonTeamKRYdsTD
2026Michigan81700

Defense

SeasonTeamTklSoloTFLSacksPDHur
2024Michigan220000
2025Michigan220000
2026Michigan110000
Career550000

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2023Michigan24RBFr.
2024Michigan24RBSo.
2025Michigan24RBJr.
2026Michigan24RBSr.5′11″210

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
2025Michigan840.0433rd (n=576)0.103.617%0.17
2026Michigan110.22––2.4––

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
2025Michigan55%3.001.100.5020%

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 Michigan 6 games, 8 returns, 170 yards
DateOpponentResultCarRush ydsRush TDKRYds
Sep 5vs.Western MichiganW 13–⁠12–––118
Sep 12vs.OklahomaW 17–⁠103120124
Sep 19vs.UTEPW 52–⁠175140123
Sep 26vs.IowaL 19–⁠20150253
Oct 3atMinnesotaL 14–⁠20–––236
Oct 17vs.Penn StateW 21–⁠182381116
2025 Michigan 8 games, 326 rushing yards, 4 TD
DateOpponentResultCarRush ydsRush TDKRYds
Sep 13vs.Central MichiganW 63–⁠35301––
Sep 20atNebraskaW 30–⁠27–––––
Oct 11atUSCL 13–⁠31100––
Nov 1vs.PurdueW 21–⁠164230––
Nov 15vs.NorthwesternW 24–⁠2215530––
Nov 22atMarylandW 45–⁠20201003––
Nov 29vs.Ohio StateL 9–⁠2711380––
Dec 31 ✦vs.TexasL 27–⁠4120820––
2024 Michigan 2 games, 2 tackles
DateOpponentResultCarRush ydsRush TDKRYds
Nov 23vs.NorthwesternW 50–⁠6–––––
Dec 31 ✦vs.AlabamaW 19–⁠13–––––

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.