Linebacker, Washington State, 2013–⁠17

Nate DeRider

Number
No. 54
Height
6′1″
Weight
231 lb
Hometown
Bellevue, WA

Nate DeRider played linebacker at Washington State (2013–⁠17).

Defense

Tackles, season by season, with his team’s record
SeasonTeamTklSoloTFLSacksIntPDHur
2016Washington State11611100
2017Washington State21101.50000
Career32162.51100

Season lines from CollegeFootballData, regular season and bowls. A dash: the source has no number for that season (often an FCS season), and career totals count only the numbers on file.

Defense before 2016

SeasonGSoloAstTkl
20158 of 13224

Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources: ESPN play-by-play participants, via SportsDataverse: tackles only, counted in the games whose play-by-play names tacklers (G: those games, of his team’s), so part of the season, not its total. A dash: the source has no number for it.

On the roster

SeasonTeamNo.PosHtWt
2013Washington State54LB
2014Washington State54LB
2015Washington State54LB
2016Washington State54LB
2017Washington State54LB6′1″231

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.

Game by game

2017 Washington State 5 games, 21 tackles
DateOpponentResultTklSoloTFLSacksIntPD
Sep 2vs.Montana StateW 31–⁠0210000
Sep 16vs.Oregon StateW 52–⁠23531000
Sep 23vs.NevadaW 45–⁠7410000
Sep 29vs.USCW 30–⁠27530000
Oct 7atOregonW 33–⁠10520.5000
2016 Washington State 7 games, 11 tackles, 1 sack, 1 INT
DateOpponentResultTklSoloTFLSacksIntPD
Sep 10atBoise StateL 28–⁠31210000
Oct 1vs.OregonW 51–⁠33110000
Oct 15vs.UCLAW 27–⁠21110000
Oct 22atArizona StateW 37–⁠32110000
Oct 29atOregon StateW 35–⁠31110000
Nov 5vs.ArizonaW 69–⁠7100000
Nov 12vs.CaliforniaW 56–⁠21411110

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.