Receiver, Virginia Tech, 2023–⁠26

Ayden Greene

Number
No. 0
Height
6′1″
Weight
194 lb
Class (2026)
Senior
Hometown
Knoxville, TN

Ayden Greene plays receiver for Virginia Tech. Last time out, against Georgia Tech: 1 catch, 5 yards.

2026 so far

15 catches, 280 yards, 2 TD

Last game: 1 catch, 5 yards vs. Georgia Tech, W 34–⁠24

Next game: at Clemson, Oct 24

Game by game this season, receiving yards
  1. 23VMI
  2. 44ODU
  3. 58@MD
  4. 88PITT
  5. 62@CAL
  6. 5GT

Filled bars: wins; outlined: losses.

Career highs

6catches, career highvs. Minnesota, 2024115receiving yards, career highvs. Minnesota, 2024

Receiving

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

* The season in progress, so far.

SeasonTeamRecYdsAvgTDLong
2023Virginia Tech55611.2019
2024Virginia Tech1926814.1267
2025Virginia Tech3151616.6367
2026Virginia Tech1528018.7248
Career701,12016.0767

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2023Virginia Tech0WRFr.
2024Virginia Tech0WRSo.
2025Virginia Tech0WRJr.
2026Virginia Tech0WRSr.6′1″194

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/playPctileMedianTotalUsage
2023Virginia Tech50.63––3.1–
2024Virginia Tech300.6215th (n=581)0.9218.75%
2025Virginia Tech580.4854th (n=1040)0.4627.88%
2026Virginia Tech231.0096th (n=829)0.4323.05%

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). From CollegeFootballData, 2013 on.

Game by game

2026 Virginia Tech 6 games, 15 catches, 280 yards, 2 TD
DateOpponentResultRecYdsTDLongRush
Sep 5vs.VMIW 73–⁠332309–
Sep 12vs.Old DominionW 44–⁠21144044–
Sep 19atMarylandW 35–⁠26458019–
Oct 2vs.PittsburghL 33–⁠35488148–
Oct 10atCaliforniaL 20–⁠25262132–
Oct 17vs.Georgia TechW 34–⁠241505–
2025 Virginia Tech 11 games, 31 catches, 516 yards, 3 TD
DateOpponentResultRecYdsTDLongRush
Aug 31vs.South CarolinaL 11–⁠24571036–
Sep 6vs.VanderbiltL 20–⁠4421005–
Sep 13vs.Old DominionL 26–⁠45167067–
Sep 20vs.WoffordW 38–⁠6452118–
Sep 27atNC StateW 23–⁠21344036–
Oct 4vs.Wake ForestL 23–⁠30215015–
Oct 11atGeorgia TechL 20–⁠35472036–
Oct 24vs.CaliforniaW 42–⁠34234127–
Nov 1vs.LouisvilleL 16–⁠28117017–
Nov 15atFlorida StateL 14–⁠34239131–
Nov 22vs.MiamiL 17–⁠34595039–
2024 Virginia Tech 10 games, 19 catches, 268 yards, 2 TD
DateOpponentResultRecYdsTDLongRush
Sep 21vs.RutgersL 23–⁠26125025–
Sep 27atMiamiL 34–⁠38333116–
Oct 5atStanfordW 31–⁠7225014–
Oct 17vs.Boston CollegeW 42–⁠2111401425
Oct 26vs.Georgia TechW 21–⁠6––––14
Nov 2atSyracuseL 31–⁠3811013
Nov 9vs.ClemsonL 14–⁠24219114–
Nov 23atDukeL 28–⁠31––––20
Nov 30vs.VirginiaW 37–⁠173360151
Jan 3 ✦vs.MinnesotaL 10–⁠2461150673
2023 Virginia Tech 4 games, 5 catches, 56 yards
DateOpponentResultRecYdsTDLongRush
Sep 16atRutgersL 16–⁠35224012–
Sep 23atMarshallL 17–⁠241505–
Nov 11atBoston CollegeW 48–⁠221808–
Dec 27 ✦vs.TulaneW 41–⁠20119019–

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.