Defensive end, Purdue, 2013–⁠16

Evan Panfil

Number
No. 95
Height
6′4″
Hometown
New Lenox, IL

Evan Panfil played defensive end at Purdue (2013–⁠16).

Career highs

2sacks, career hightwice; last vs. Iowa, 2016

Defense

SeasonTeamTklSoloTFLSacksPDHur
2016Purdue321812500

Season lines from CollegeFootballData, regular season and bowls.

Defense before 2016

SeasonGSoloAstTklTFL
2013N75051
2015E8 of 1261117–

Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources, marked by season: N, NCAA statistics, via octonion/football, the season’s official lines (G: games played); E, 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.PosHt
2013Purdue95DE
2014Purdue95DE
2015Purdue95DE
2016Purdue95DE6′4″

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 Purdue 11 games, 32 tackles, 5 sacks
DateOpponentResultTklSoloTFLSacksPD
Sep 3vs.Eastern KentuckyW 45–⁠24300.500
Sep 10vs.CincinnatiL 20–⁠3821000
Sep 24vs.NevadaW 24–⁠1455420
Oct 8atIllinoisW 34–⁠3130000
Oct 15vs.IowaL 35–⁠4933220
Oct 22atNebraskaL 14–⁠2743300
Oct 29vs.Penn StateL 24–⁠6211110
Nov 5atMinnesotaL 31–⁠44420.500
Nov 12vs.NorthwesternL 17–⁠4510000
Nov 19vs.WisconsinL 20–⁠4931000
Nov 26atIndianaL 24–⁠2632100

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

Before the draft

DrillPro day 2017
Height6′4⅜″
Weight280 lb
Arm length32″
Hand size9⅜″
40-yard dash5.02 s
Vertical jump28½″
Broad jump9′1″
Bench press23 reps
3-cone drill7.31 s
20-yard shuttle4.65 s

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.