Linebacker, Colorado State, 2013–⁠17

Patrick Elsenbast

Number
No. 42
Height
6′0″
Weight
210 lb
Hometown
Littleton, CO

Patrick Elsenbast played linebacker at Colorado State (2013–⁠17).

Defense

Tackles, season by season, with his team’s record
SeasonTeamTklSoloTFLSacksPDHur
2016Colorado State37260010
2017Colorado State960000
Career46320010

Season lines from CollegeFootballData, regular season and bowls.

Defense before 2016

SeasonGSoloTkl
201512 of 1322

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
2013Colorado State42LB
2014Colorado State42LB
2015Colorado State42LB
2016Colorado State42LB
2017Colorado State42LB6′0″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.

Game by game

2017 Colorado State 5 games, 9 tackles
DateOpponentResultTklSoloTFLSacksPD
Sep 16atAlabamaL 23–⁠4111000
Oct 7atUtah StateW 27–⁠1422000
Oct 20atNew MexicoW 27–⁠2442000
Nov 11vs.Boise StateL 52–⁠5911000
Nov 18vs.San José StateW 42–⁠1410000
2016 Colorado State 11 games, 37 tackles
DateOpponentResultTklSoloTFLSacksPD
Sep 2vs.ColoradoL 7–⁠4422000
Sep 10vs.UTSAW 23–⁠1464000
Sep 24atMinnesotaL 24–⁠3131000
Oct 1vs.WyomingL 17–⁠3831000
Oct 8vs.Utah StateW 31–⁠2421000
Oct 15atBoise StateL 23–⁠2843000
Oct 22atUNLVW 42–⁠2322000
Nov 5vs.Fresno StateW 37–⁠064001
Nov 19vs.New MexicoW 49–⁠3122000
Nov 26atSan Diego StateW 63–⁠3155000
Dec 22 ✦vs.IdahoL 50–⁠6121000

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.