Thomas Tyner, 2013
Photo: Tim Hipps, Public domain, via Wikimedia Commons

Running back, Oregon State (from Oregon), 2013–⁠17

Thomas Tyner

Number
No. 4
Height
5′11″
Weight
232 lb
Hometown
Aloha, OR

Thomas Tyner played running back at Oregon (2013–⁠15) and Oregon State (2017).

Career highs

140rushing yards, career highvs. Oregon State, 20132rushing touchdowns, career highfour times; last vs. Florida State, 2014

Team titles: Pac-12 champions, 2014

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2013Oregon1157116.2966
2014Oregon1135735.1523
2017Oregon State642974.6321
Career2921,5815.41766

Receiving

SeasonTeamRecYdsAvgTDLong
2013Oregon141349.6023
2014Oregon11676.1121
2017Oregon State5428.4016
Career302438.1123

Returns

SeasonTeamKRYdsTD
2014Oregon71510

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHtWt
2013Oregon4RB
2014Oregon4RB
2015Oregon4RB
2017Oregon State4RB5′11″232

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
2013Oregon1180.2494th (n=226)0.0728.614%0.12
2014Oregon1270.1663rd (n=253)0.1220.116%0.28
2017Oregon State710.1456th (n=287)0.1210.311%0.08

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.

Game by game

2017 Oregon State 10 games, 297 rushing yards, 3 TD
DateOpponentResultCarYdsTDLongRecRec yds
Aug 26atColorado StateL 27–⁠584807––
Sep 2vs.Portland StateW 35–⁠3221008––
Sep 30vs.WashingtonL 7–⁠4295411816
Oct 7atUSCL 10–⁠38723011––
Oct 14vs.ColoradoL 33–⁠365310917
Oct 26vs.StanfordL 14–⁠15952118––
Nov 4atCaliforniaL 23–⁠3784112115
Nov 11atArizonaL 28–⁠4974201118
Nov 18vs.Arizona StateL 24–⁠4051308116
Nov 25atOregonL 10–⁠69823011––
2014 Oregon 11 games, 573 rushing yards, 5 TD
DateOpponentResultCarYdsTDLongRecRec yds
Aug 30vs.South DakotaW 62–⁠13116401538
Sep 6vs.Michigan StateW 46–⁠27133311127
Sep 13vs.WyomingW 48–⁠141158011216
Sep 20atWashington StateW 38–⁠3152007––
Oct 2vs.ArizonaL 24–⁠311046022––
Oct 11atUCLAW 42–⁠30135809121
Oct 18vs.WashingtonW 45–⁠203001113
Nov 1vs.StanfordW 45–⁠161063221––
Nov 8atUtahW 51–⁠271245011––
Jan 1 ✦vs.Florida StateW 59–⁠2013124223––
Jan 12 ✦vs.Ohio StateL 20–⁠42126201222
2013 Oregon 12 games, 711 rushing yards, 9 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 7atVirginiaW 59–⁠10451231––
Sep 14vs.TennesseeW 59–⁠14829114––
Sep 28vs.CaliforniaW 55–⁠16139412113
Oct 5atColoradoW 57–⁠161030122229
Oct 12atWashingtonW 45–⁠241257015224
Oct 19vs.Washington StateW 62–⁠38799266342
Oct 26vs.UCLAW 42–⁠14147711417
Nov 7atStanfordL 20–⁠261202––
Nov 16vs.UtahW 44–⁠21757027––
Nov 23atArizonaL 16–⁠42115301434
Nov 29vs.Oregon StateW 36–⁠3522140140––
Dec 30 ✦vs.TexasW 30–⁠762209225

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.