Tight end, Oregon State (from Utah Tech), 2022–⁠26

Eric Olsen

Number
No. 80
Height
6′5″
Weight
240 lb
Class (2026)
Senior
Hometown
St. George, UT

Eric Olsen plays tight end for Oregon State, after Utah Tech (2022–⁠25). Last time out, against Washington State: 3 catches, 73 yards; 1 tackles.

2026 so far

30 catches, 353 yards, 3 TD

Last game: 3 catches, 73 yards; 1 tackles vs. Washington State, W 48–⁠30

Next game: at Fresno State, Oct 31

Game by game this season, receiving yards
  1. 54@HOU
  2. 3TTU
  3. 35MONT
  4. 79@UTEP
  5. 65@CSU
  6. 44SDSU
  7. 73WSU

Filled bars: wins; outlined: losses.

Career highs

9catches, career highat Colorado State, 2026107receiving yards, career highat Central Arkansas, 20252receiving touchdowns, career highat Colorado State, 2026

Receiving

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

* The season in progress, so far.

SeasonTeamRecYdsAvgTDLong
2024Utah Tech1725515.0153
2025Utah Tech5156611.1249
2026Oregon State3035311.8340
Career981,17412.0653

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2022Utah Tech80TERS
2024Utah Tech80TESo.
2025Utah Tech80TEJr.
2026Oregon State80TESr.6′5″240

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
2024Utah Tech (FCS)180.52––9.4–
2025Utah Tech (FCS)1050.1510th (n=1040)0.4615.513%
2026Oregon State380.5869th (n=829)0.4322.28%

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 Oregon State 7 games, 30 catches, 353 yards, 3 TD
DateOpponentResultRecYdsTDLongRush
Sep 5atHoustonL 20–⁠33454024–
Sep 12vs.Texas TechL 24–⁠353304–
Sep 19vs.MontanaW 52–⁠17335119–
Sep 26atUTEPW 33–⁠7579040–
Oct 3atColorado StateW 56–⁠26965212–
Oct 10vs.San Diego StateW 66–⁠14344029–
Oct 17vs.Washington StateW 48–⁠30373032–
2025 Utah Tech 12 games, 51 catches, 566 yards, 2 TD
DateOpponentResultRecYdsTDLongRush
Aug 30vs.UC DavisL 24–⁠316461316
Sep 6atNorthern ArizonaL 31–⁠38323013–
Sep 13atIdahoL 6–⁠20545013–
Sep 20vs.Northern IowaW 20–⁠9311060
Sep 27atAustin PeayL 10–⁠42346035–
Oct 4atCentral ArkansasL 17–⁠235107149–
Oct 11vs.Tarleton StateL 23–⁠41675017–
Oct 25vs.Southern UtahL 7–⁠28659020–
Nov 1vs.North AlabamaW 34–⁠3334002918
Nov 8atAbilene ChristianL 10–⁠31213078
Nov 15atWest GeorgiaL 0–⁠23683043−1
Nov 22vs.Eastern KentuckyL 10–⁠3331808–
2024 Utah Tech 9 games, 17 catches, 255 yards, 1 TD
DateOpponentResultRecYdsTDLongRush
Aug 31vs.Montana StateL 7–⁠3115052
Sep 7atUNLVL 14–⁠72429024–
Sep 14vs.Northern ArizonaL 17–⁠45236020–
Sep 28vs.Abilene ChristianL 30–⁠55360132–
Oct 5atNorth AlabamaL 14–⁠601−400–
Oct 26atEastern KentuckyL 17–⁠28––––10
Nov 2vs.Central ArkansasW 34–⁠21226022−2
Nov 16vs.West GeorgiaL 31–⁠34267053–
Nov 23atSouthern UtahL 34–⁠372360274

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.