Linebacker, Arizona State, 2015–⁠18

Koron Crump

Number
No. 4
Height
6′3″
Weight
215 lb
Class (2018)
Senior
Hometown
St. Louis, MO

Koron Crump played linebacker at Arizona State (2015–⁠18).

Career highs

10tackles, career highat Oregon, 20163sacks, career highvs. Washington State, 2016

Defense

Tackles, season by season, with his team’s record
SeasonTeamTklSoloTFLSacksIntPDHur
2016Arizona State372810.59101
2017Arizona State131144000
2018Arizona State6300001
Career564214.513102

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.

On the roster

SeasonTeamNo.PosClassHtWt
2015Arizona State4LBFr.
2016Arizona State4LBSo.
2017Arizona State4LBJr.
2018Arizona State4LBSr.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.

Game by game

2018 Arizona State 4 games, 6 tackles
DateOpponentResultTklSoloTFLSacksIntPD
Sep 1vs.UTSAW 49–⁠7110000
Sep 15atSan Diego StateL 21–⁠28320000
Sep 29vs.Oregon StateW 52–⁠24100000
Oct 6atColoradoL 21–⁠28100000
2017 Arizona State 3 games, 13 tackles, 4 sacks
DateOpponentResultTklSoloTFLSacksIntPD
Aug 31vs.New Mexico StateW 37–⁠31662200
Sep 9vs.San Diego StateL 20–⁠30652200
Sep 16atTexas TechL 45–⁠52100000
2016 Arizona State 11 games, 37 tackles, 9 sacks, 1 INT
DateOpponentResultTklSoloTFLSacksIntPD
Sep 3vs.Northern ArizonaW 44–⁠13111000
Sep 10vs.Texas TechW 68–⁠55331100
Sep 16atUTSAW 32–⁠28110000
Sep 24vs.CaliforniaW 51–⁠41222200
Oct 1atUSCL 20–⁠41210000
Oct 8vs.UCLAW 23–⁠20332200
Oct 15atColoradoL 16–⁠40430000
Oct 22vs.Washington StateL 32–⁠37443300
Oct 29atOregonL 35–⁠541051.5100
Nov 19atWashingtonL 18–⁠44420010
Nov 25atArizonaL 35–⁠56330000

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.