Receiver, Utah State (from Virginia), 2022–⁠26

Eli Wood

Number
No. 7
Height
6′2″
Weight
210 lb
Class (2026)
Senior
Hometown
Lynchburg, VA

Eli Wood plays receiver for Utah State, after Virginia (2022–⁠25). Last time out, against Washington State: 6 catches, 84 yards, 1 TD. Wood leads Utah State in receiving touchdowns and receiving yards this season.

2026 so far

36 catches, 472 yards, 5 TD

Last game: 6 catches, 84 yards, 1 TD vs. Washington State, W 17–⁠16

Next game: at Texas State, Oct 24

Game by game this season, receiving yards
  1. 90IDST
  2. 53@WASH
  3. 47@UTAH
  4. 96TROY
  5. 102@BOIS
  6. 84WSU

Filled bars: wins; outlined: losses.

Career highs

7catches, career hightwice; last at Boise State, 2026102receiving yards, career highat Boise State, 2026

Receiving

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

* The season in progress, so far.

SeasonTeamRecYdsAvgTDLong
2024Virginia3155.006
2025Virginia1620512.8238
2026Utah State3647213.1533
Career5569212.6738

Defense

SeasonTeamTklSoloTFLSacksPDHur
2022Virginia220000
2023Virginia110000
2024Virginia310000
2025Virginia870000
2026Utah State110000
Career15120000

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2022Virginia7WRYr 1
2023Virginia7WRYr 2
2024Virginia7WRYr 3
2025Virginia7WRYr 4
2026Utah State7WRSr. (Yr 5)6′2″210

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
2024Virginia10.79––0.8–
2025Virginia250.86––21.54%
2026Utah State570.5868th (n=829)0.4333.215%

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 Utah State 6 games, 36 catches, 472 yards, 5 TD
DateOpponentResultRecRec ydsRec TDTklSacksPD
Sep 5vs.Idaho StateL 17–⁠296901–––
Sep 12atWashingtonL 14–⁠166531100
Sep 19atUtahL 0–⁠334470–––
Sep 26vs.TroyW 21–⁠107961–––
Oct 3atBoise StateL 18–⁠3771021–––
Oct 9vs.Washington StateW 17–⁠166841–––
2025 Virginia 10 games, 16 catches, 205 yards, 2 TD
DateOpponentResultRecRec ydsRec TDTklSacksPD
Sep 6atNC StateL 31–⁠351100100
Sep 20vs.StanfordW 48–⁠20141–––
Sep 26vs.Florida StateW 46–⁠382290–––
Oct 4atLouisvilleW 30–⁠27–––100
Nov 1atCaliforniaW 31–⁠212460100
Nov 8vs.Wake ForestL 9–⁠16150–––
Nov 15atDukeW 34–⁠17130–––
Nov 29vs.Virginia TechW 27–⁠7170300
Dec 6vs.DukeL 20–⁠273301–––
Dec 27 ✦vs.MissouriW 13–⁠74710200
2024 Virginia 4 games, 3 catches, 15 yards
DateOpponentResultRecRec ydsRec TDTklSacksPD
Aug 31vs.RichmondW 34–⁠13290–––
Oct 26vs.North CarolinaL 14–⁠41160–––
Nov 9atPittsburghW 24–⁠19–––100
Nov 16atNotre DameL 14–⁠35–––200
2023 Virginia 1 game, 1 tackle
DateOpponentResultRecRec ydsRec TDTklSacksPD
Sep 22vs.NC StateL 21–⁠24–––100
2022 Virginia 1 game, 2 tackles
DateOpponentResultRecRec ydsRec TDTklSacksPD
Nov 12vs.PittsburghL 7–⁠37–––200

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.