Receiver, South Florida, 2012–⁠16

Alex Mut

Number
No. 84
Height
6′3″
Hometown
Port Charlotte, FL

Alex Mut played receiver at South Florida (2012–⁠16).

Receiving

SeasonTeamRecYdsAvgTDLong
2016South Florida231.505

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHt
2012South Florida84WR
2013South Florida84WR
2014South Florida84WR
2015South Florida84WR
2016South Florida84WR6′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.

Per play

SeasonTeamPlaysEPA/playPctileMedianTotalUsage
2016South Florida2-0.25––-0.5–

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

2016 South Florida 2 games, 2 catches, 3 yards
DateOpponentResultRecYdsTDLong
Sep 3vs.TowsonW 56–⁠201−20−2
Oct 1atCincinnatiW 45–⁠201505

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.