Receiver, Kansas State, 2018–⁠20

Dylan Wentzel

Lettered 2019 (school media guide)

Number
No. 24
Height
6′0″
Weight
176 lb
Class (2020)
Junior
Hometown
Salina, KS

Dylan Wentzel played receiver at Kansas State (2018–⁠20).

Rushing

SeasonTeamCarYdsAvgTDLong
2019Kansas State177.007

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2018Kansas State24WRFr.
2019Kansas State24WRSo.
2020Kansas State24WRJr.6′0″176

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.

Per play

SeasonTeamPlaysEPA/playPctileMedianTotalUsage
2019Kansas State11.11––1.1–

Expected points added: how much the player’s plays moved the team’s expected score, per play and in total. Plays: total EPA divided by EPA per play, the plays the source credits to him (for a receiver roughly his catches and runs, not every target; for a passer, not every attempt), so it can differ from attempts plus carries. Percentile: against the position’s regulars that season across all divisions on file (quarterbacks with 150+ plays, backs 60+, receivers and tight ends 30+), with how many there were (n) and their median; a dash means too few plays to rank. A season in progress uses the full-season bar scaled by games played, never below 75 plays for quarterbacks, 30 for backs and 20 for receivers. The cohort grows or shrinks with the source’s coverage each season (2025 lists far more players), so compare percentiles rather than raw EPA across years. FCS seasons are marked. Usage: the share of the team’s plays the player was part of (shown from 20 plays). From CollegeFootballData, 2013 on.

Game by game

2019 Kansas State 1 game, 7 rushing yards
DateOpponentResultCarYdsTDLong
Aug 31vs.NichollsW 49–⁠141707

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.