Cornerback, Purdue, 2014–⁠18

Tim Cason

Number
No. 24
Height
6′0″
Weight
195 lb
Class (2018)
Senior
Hometown
Clarkston, MI

Tim Cason played cornerback at Purdue (2014–⁠18).

Defense

Tackles, season by season, with his team’s record
SeasonTeamTklSoloTFLSacksPDHur
2016Purdue17130010
2017Purdue330010
2018Purdue1290.5040
Career32250.5060

Season lines from CollegeFootballData, regular season and bowls.

Defense before 2016

SeasonGSoloAstTkl
20158 of 12224

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.PosClassHtWt
2014Purdue24CBRS
2015Purdue24CBFr.
2016Purdue24CBSo.
2017Purdue24CBJr.
2018Purdue24CBSr.6′0″195

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

2018 Purdue 8 games, 12 tackles
DateOpponentResultTklSoloTFLSacksPD
Aug 30vs.NorthwesternL 27–⁠3122003
Sep 8vs.Eastern MichiganL 19–⁠2011000
Sep 22vs.Boston CollegeW 30–⁠13210.500
Sep 29atNebraskaW 42–⁠2810000
Oct 13atIllinoisW 46–⁠711000
Oct 20vs.Ohio StateW 49–⁠2032000
Nov 17vs.WisconsinL 44–⁠4711000
Nov 24atIndianaW 28–⁠2111001
2017 Purdue 2 games, 3 tackles
DateOpponentResultTklSoloTFLSacksPD
Nov 4vs.IllinoisW 29–⁠1022000
Nov 11atNorthwesternL 13–⁠2311001
2016 Purdue 6 games, 17 tackles
DateOpponentResultTklSoloTFLSacksPD
Sep 3vs.Eastern KentuckyW 45–⁠2443000
Sep 10vs.CincinnatiL 20–⁠3843001
Sep 24vs.NevadaW 24–⁠1432000
Oct 15vs.IowaL 35–⁠4932000
Oct 22atNebraskaL 14–⁠2722000
Oct 29vs.Penn StateL 24–⁠6211000

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.