Running back, Purdue, 2024–⁠26

Antonio Harris

Number
No. 22
Height
6′1″
Weight
215 lb
Class (2026)
Junior
Hometown
Chandler, IN

Antonio Harris plays running back for Purdue. Last time out, against Washington: 4 carries, 65 yards, 1 TD; 1 catch, 7 yards.

2026 so far

156 rushing yards, 2 TD

Last game: 4 carries, 65 yards, 1 TD; 1 catch, 7 yards vs. Washington, L 26–⁠38

Next game: at Penn State, Oct 31

Game by game this season, rushing yards
  1. 32INST
  2. 16ND
  3. 20@ILL
  4. 23MINN
  5. 65WASH

Filled bars: wins; outlined: losses.

Rushing

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

* The season in progress, so far.

SeasonTeamCarYdsAvgTDLong
2024Purdue144.004
2025Purdue693054.4241
2026Purdue271565.8259
Career974654.8459

Receiving

SeasonTeamRecYdsAvgTDLong
2025Purdue171378.1022
2026Purdue35819.3047
Career201959.8047

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2024Purdue22RBFr.
2025Purdue22RBSo.
2026Purdue22RBJr.6′1″215

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
2024Purdue1-0.12––-0.1––
2025Purdue900.1152nd (n=576)0.109.512%0.14
2026Purdue300.10––2.97%–

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
2025Purdue36%2.600.701.3025%
2026Purdue42%3.100.700.108%

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 Purdue 6 games, 156 rushing yards, 2 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 4vs.Indiana StateW 44–⁠196320–––
Sep 19atUCLAL 38–⁠52–––1470
Sep 26vs.Notre DameL 10–⁠493160–––
Oct 3atIllinoisW 24–⁠176201140
Oct 10vs.MinnesotaW 41–⁠138230–––
Oct 16vs.WashingtonL 26–⁠384651170
2025 Purdue 12 games, 305 rushing yards, 2 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Aug 30vs.Ball StateW 31–⁠031201220
Sep 6vs.Southern IllinoisW 34–⁠175260–––
Sep 13vs.USCL 17–⁠331−201150
Sep 20atNotre DameL 30–⁠563502200
Oct 4vs.IllinoisL 27–⁠434691150
Oct 11atMinnesotaL 20–⁠27200160
Oct 18atNorthwesternL 0–⁠19––––––
Oct 25vs.RutgersL 24–⁠2724201180
Nov 1atMichiganL 16–⁠2111541120
Nov 8vs.Ohio StateL 10–⁠34134503190
Nov 15atWashingtonL 13–⁠49102303120
Nov 28vs.IndianaL 3–⁠56153103180
2024 Purdue 1 game, 4 rushing yards
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Nov 16vs.Penn StateL 10–⁠49140–––

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.