Defensive end, Virginia Tech, 2012–⁠16

Ken Ekanem

Number
No. 4
Height
6′3″
Hometown
Centreville, VA

Ken Ekanem played defensive end at Virginia Tech (2012–⁠16).

Career highs

2sacks, career highvs. East Carolina, 2016

Defense

SeasonTeamTklSoloTFLSacksPDHur
2016Virginia Tech3620107.5211

Season lines from CollegeFootballData, regular season and bowls.

Defense before 2016

SeasonGSoloAstTkl
201311123

Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources: NCAA statistics, via octonion/football, the season’s official lines (G: games played). A dash: the source has no number for it.

On the roster

SeasonTeamNo.PosHt
2012Virginia Tech4DE
2013Virginia Tech4DE
2014Virginia Tech4DE
2015Virginia Tech4DE
2016Virginia Tech4DE6′3″

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

2016 Virginia Tech 13 games, 36 tackles, 7.5 sacks
DateOpponentResultTklSoloTFLSacksPD
Sep 3vs.LibertyW 36–⁠1343110
Sep 10vs.TennesseeL 24–⁠45531.51.51
Sep 17vs.Boston CollegeW 49–⁠031100
Sep 24vs.East CarolinaW 54–⁠1751220
Oct 8atNorth CarolinaW 34–⁠300001
Oct 15atSyracuseL 17–⁠3122000
Oct 27atPittsburghW 39–⁠3611000
Nov 5atDukeW 24–⁠2111000
Nov 12vs.Georgia TechL 20–⁠3020000
Nov 19atNotre DameW 34–⁠3162210
Nov 26vs.VirginiaW 52–⁠1022110
Dec 3vs.ClemsonL 35–⁠42430.500
Dec 29 ✦vs.ArkansasW 35–⁠2411110

Box scores from CollegeFootballData, 2004 on. ✦ postseason; ★ a career high on file.

Before the draft

DrillCombine 2017Combine or pro day 2017
Height6′2¾″
Weight257 lb
Arm length32″
Hand size10½″
40-yard dash4.88 s
10-yard split1.68 s
Vertical jump30½″
Broad jump9′7″
Bench press20 reps
3-cone drill7.38 s
20-yard shuttle4.58 s

Combine or pro day: the source doesn’t say which. Combine and pro day results compiled by array-carpenter (nfl-draft-data).

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.