Running back, Virginia Tech, 2025–⁠26

Marcellous Hawkins

Number
No. 27
Height
5′10″
Weight
223 lb
Class (2026)
Senior
Hometown
Oklahoma City, OK

Marcellous Hawkins plays running back for Virginia Tech. Last time out, against Georgia Tech: 9 carries, 42 yards; 1 catch, −1 yard.

2026 so far

325 rushing yards, 5 TD

Last game: 9 carries, 42 yards; 1 catch, −1 yard vs. Georgia Tech, W 34–⁠24

Next game: at Clemson, Oct 24

Game by game this season, rushing yards
  1. 69VMI
  2. 43ODU
  3. 75@MD
  4. 19@BC
  5. 32PITT
  6. 45@CAL
  7. 42GT

Filled bars: wins; outlined: losses.

Career highs

167rushing yards, career highvs. California, 20253rushing touchdowns, career highvs. VMI, 2026

Rushing

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

* The season in progress, so far.

SeasonTeamCarYdsAvgTDLong
2025Virginia Tech1187496.3140
2026Virginia Tech783254.2520
Career1961,0745.5640

Receiving

SeasonTeamRecYdsAvgTDLong
2025Virginia Tech12746.2119
2026Virginia Tech8415.1015
Career201155.8119

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2025Virginia Tech27RBJr.
2026Virginia Tech27RBSr.5′10″223

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
2025Virginia Tech1320.1770th (n=576)0.1022.218%0.22
2026Virginia Tech90.13––1.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
2025Virginia Tech54%3.801.501.6015%

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 Virginia Tech 7 games, 325 rushing yards, 5 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 5vs.VMIW 73–⁠31269314––
Sep 12vs.Old DominionW 44–⁠211143120218
Sep 19atMarylandW 35–⁠261675014215
Sep 26atBoston CollegeW 21–⁠14101906––
Oct 2vs.PittsburghL 33–⁠3583209211
Oct 10atCaliforniaL 20–⁠2512451111−2
Oct 17vs.Georgia TechW 34–⁠249420151−1
2025 Virginia Tech 11 games, 749 rushing yards, 1 TD
DateOpponentResultCarYdsTDLongRecRec yds
Aug 31vs.South CarolinaL 11–⁠241558011––
Sep 6vs.VanderbiltL 20–⁠4482909210
Sep 13vs.Old DominionL 26–⁠4542107412
Sep 20vs.WoffordW 38–⁠61379026227
Sep 27atNC StateW 23–⁠21447025111
Oct 4vs.Wake ForestL 23–⁠301148116––
Oct 11atGeorgia TechL 20–⁠35982028––
Oct 24vs.CaliforniaW 42–⁠3421167034––
Nov 1vs.LouisvilleL 16–⁠281345011112
Nov 15atFlorida StateL 14–⁠34121010401−5
Nov 22vs.MiamiL 17–⁠3487203317

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.