Tight end, Nevada, 2022–⁠23

Dyson Frank

Number
No. 86
Height
6′6″
Weight
253 lb
Class (2023)
Sophomore
Hometown
Alpine, UT

Dyson Frank played tight end at Nevada (2022–⁠23).

Receiving

SeasonTeamRecYdsAvgTDLong
2022Nevada3279.0016

Defense

SeasonTeamTklSoloTFLSacksPDHur
2022Nevada110000

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2022Nevada86TEFr.
2023Nevada86TESo.6′6″253

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
2022Nevada10.36––0.4–

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

2022 Nevada 2 games, 3 catches, 27 yards
DateOpponentResultRecRec ydsRec TDTklSacksPD
Sep 10vs.Incarnate WordL 41–⁠55170–––
Nov 26atUNLVL 22–⁠272200100

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.