Running back, Virginia, 2023–⁠26

Noah Vaughn

Number
No. 3
Height
5′9″
Weight
196 lb
Class (2026)
Senior
Hometown
Maryville, TN

Noah Vaughn plays running back for Virginia.

2026 so far

141 rushing yards

Last game: vs. Syracuse, W 28–⁠25

Next game: vs. Duke, Oct 23

Game by game this season, rushing yards
  1. 21NCSU
  2. 81NORF
  3. 12WVU
  4. 21DEL
  5. 6@FSU
  6. 0SYR

Filled bars: wins; outlined: losses.

Career highs

101rushing yards, career highvs. William & Mary, 2025

Rushing

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

* The season in progress, so far.

SeasonTeamCarYdsAvgTDLong
2024Virginia361203.3013
2025Virginia231747.6054
2026Virginia281415.0021
Career874355.0054

Receiving

SeasonTeamRecYdsAvgTDLong
2024Virginia10777.7013
2026Virginia166.006
Career11837.5013

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2023Virginia3RBFr.
2024Virginia3RBSo.
2025Virginia3RBJr.
2026Virginia3RBSr.5′9″196

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
2024Virginia470.13––6.08%0.12
2025Virginia230.49––11.47%–
2026Virginia310.02––0.77%–

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
2025Virginia65%4.201.302.805%
2026Virginia50%3.401.300.7018%

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 6 games, 141 rushing yards
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Aug 29vs.NC StateW 34–⁠86210–––
Sep 11vs.Norfolk StateW 59–⁠38810160
Sep 19vs.West VirginiaL 27–⁠384120–––
Sep 26vs.DelawareW 42–⁠36210–––
Oct 3atFlorida StateL 7–⁠38360–––
Oct 10vs.SyracuseW 28–⁠25100–––
2025 Virginia 4 games, 174 rushing yards
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Aug 30vs.Coastal CarolinaW 48–⁠710450–––
Sep 6atNC StateL 31–⁠354240–––
Sep 13vs.William & MaryW 55–⁠1681010–––
Nov 1atCaliforniaW 31–⁠21140–––
2024 Virginia 8 games, 120 rushing yards
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 14vs.MarylandL 13–⁠27240–––
Sep 21atCoastal CarolinaW 43–⁠249320160
Oct 12vs.LouisvilleL 20–⁠24150–––
Oct 19atClemsonL 31–⁠482701120
Oct 26vs.North CarolinaL 14–⁠411002140
Nov 16atNotre DameL 14–⁠3551201130
Nov 23vs.SMUL 7–⁠33104403160
Nov 30atVirginia TechL 17–⁠3761602160

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.