Receiver, Utah State, 2015–⁠18

Ron’quavion Tarver

Number
No. 1
Height
6′3″
Weight
215 lb
Class (2018)
Senior
Hometown
Belle Glade, FL

Ron’quavion Tarver played receiver at Utah State (2015–⁠18).

Career highs

9catches, career hightwice; last vs. Air Force, 2018143receiving yards, career highvs. Air Force, 20162receiving touchdowns, career highthree times; last vs. UNLV, 2018

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2016Utah State4660213.1342
2017Utah State4856911.9757
2018Utah State6670910.7842
Career1601,88011.81857

Defense

SeasonTeamTklSoloTFLSacksPDHur
2016Utah State200000
2017Utah State440000
Career640000

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2015Utah State1WRFr.
2016Utah State19WRSo.
2017Utah State1WRJr.
2018Utah State1WRSr.6′3″215

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
2017Utah State770.4537th (n=507)0.5234.28%
2018Utah State940.5553rd (n=497)0.5352.110%

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

2018 Utah State 13 games, 66 catches, 709 yards, 8 TD
DateOpponentResultRecYdsTDLongRush
Aug 31atMichigan StateL 31–⁠38329010–
Sep 8vs.New Mexico StateW 60–⁠13541015–
Sep 13vs.Tennessee TechW 73–⁠12530011–
Sep 22vs.Air ForceW 42–⁠329128029–
Oct 5atBYUW 45–⁠20318284
Oct 13vs.UNLVW 59–⁠28452229–
Oct 20atWyomingW 24–⁠161707–
Oct 27vs.New MexicoW 61–⁠197112139–
Nov 3atHawai’iW 56–⁠17540122–
Nov 10vs.San José StateW 62–⁠24874015–
Nov 17atColorado StateW 29–⁠24669028–
Nov 24atBoise StateL 24–⁠33676142–
Dec 15 ✦vs.North TexasW 52–⁠13433113–
2017 Utah State 13 games, 48 catches, 569 yards, 7 TD
DateOpponentResultRecYdsTDLongRush
Sep 1atWisconsinL 10–⁠592806–
Sep 7vs.Idaho StateW 51–⁠13775132–
Sep 16atWake ForestL 10–⁠46535013–
Sep 23atSan José StateW 61–⁠10542123–
Sep 29vs.BYUW 40–⁠24676136–
Oct 7vs.Colorado StateL 14–⁠2728059
Oct 14vs.WyomingL 23–⁠281303–
Oct 21atUNLVW 52–⁠281808–
Oct 28vs.Boise StateL 14–⁠41377157–
Nov 4atNew MexicoW 24–⁠10240031–
Nov 18vs.Hawai’iW 38–⁠0214110–
Nov 25atAir ForceL 35–⁠38486225–
Dec 29 ✦vs.New Mexico StateL 20–⁠26897041–
2016 Utah State 12 games, 46 catches, 602 yards, 3 TD
DateOpponentResultRecYdsTDLongRush
Sep 1vs.Weber StateW 45–⁠6–––––
Sep 10atUSCL 7–⁠45437015–
Sep 16vs.Arkansas StateW 34–⁠20324113–
Sep 24vs.Air ForceL 20–⁠279143042–
Oct 1atBoise StateL 10–⁠2152909–
Oct 8atColorado StateL 24–⁠31136036–
Oct 22vs.Fresno StateW 38–⁠20354125–
Oct 28vs.San Diego StateL 13–⁠40328014–
Nov 5atWyomingL 28–⁠528104024–
Nov 12vs.New MexicoL 21–⁠24684141–
Nov 19atNevadaL 37–⁠38351030–
Nov 26atBYUL 10–⁠28112012–

Box scores from CollegeFootballData, 2004 on. ✦ postseason; ★ a career high on file.

Before the draft

Played in the 2019 East–West Shrine Game (West team, won 21–⁠17).

Rosters and honors: Wikipedia (CC BY-SA).

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.