Running back, Michigan State, 2024–⁠26

Brandon Tullis

Lettered 2024–⁠25 (school media guide)

Number
No. 7
Height
6′1″
Weight
224 lb
Class (2026)
Junior
Hometown
Dallas, TX

Brandon Tullis plays running back for Michigan State. Last time out, at Wisconsin: 5 carries, 10 yards; 1 catch, 6 yards.

2026 so far

49 rushing yards

Last game: 5 carries, 10 yards; 1 catch, 6 yards at Wisconsin, L 3–⁠31

Next game: at UCLA, Oct 24

Game by game this season, rushing yards
  1. 37EMU
  2. 2NEB
  3. 10@WIS

Filled bars: wins; outlined: losses.

Rushing

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

* The season in progress, so far.

SeasonTeamCarYdsAvgTDLong
2024Michigan State7202.909
2025Michigan State682974.4435
2026Michigan State10494.9013
Career853664.3435

Receiving

SeasonTeamRecYdsAvgTDLong
2025Michigan State11827.5024
2026Michigan State166.006
Career12887.3024

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2024Michigan State7RBFr.
2025Michigan State7RBSo.
2026Michigan State7RBJr.6′1″224

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
2024Michigan State7-0.13––-0.9––
2025Michigan State840.0330th (n=576)0.102.711%0.09
2026Michigan State110.38––4.1––

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
2025Michigan State49%3.001.300.7020%

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 State 3 games, 49 rushing yards
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 12vs.Eastern MichiganW 35–⁠74370–––
Sep 26vs.NebraskaL 13–⁠31120–––
Oct 3atWisconsinL 3–⁠315100160
2025 Michigan State 12 games, 297 rushing yards, 4 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Aug 29vs.Western MichiganW 23–⁠67521–––
Sep 6vs.Boston CollegeW 42–⁠404290160
Sep 13vs.Youngstown StateW 41–⁠2473112100
Sep 20atUSCL 31–⁠456120–––
Oct 4atNebraskaL 27–⁠385401240
Oct 11vs.UCLAL 13–⁠383501110
Oct 18atIndianaL 13–⁠382301100
Oct 25vs.MichiganL 20–⁠31221160
Nov 1atMinnesotaL 20–⁠2314511–––
Nov 15vs.Penn StateL 10–⁠28160–––
Nov 22atIowaL 17–⁠208560170
Nov 29vs.MarylandW 38–⁠289460380
2024 Michigan State 3 games, 20 rushing yards
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 14vs.Prairie View A&MW 40–⁠03130–––
Sep 28vs.Ohio StateL 7–⁠382−20–––
Oct 19vs.IowaW 32–⁠20290–––

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.