Receiver, Memphis, 2014–⁠17

Phil Mayhue

Number
No. 89
Height
6′3″
Weight
210 lb
Hometown
Sicklerville, NJ

Phil Mayhue played receiver at Memphis (2014–⁠17).

Career highs

7catches, career highvs. Tulane, 2015142receiving yards, career highvs. Houston, 20162receiving touchdowns, career highvs. Houston, 2016

Team titles: American champions, 2014

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2014Memphis1524216.1254
2015Memphis5167013.1143
2016Memphis4267716.1467
2017Memphis3552114.9346
Career1432,11014.81067

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHtWt
2014Memphis89WR
2015Memphis89WR
2016Memphis89WR
2017Memphis89WR6′3″210

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
2014Memphis201.10––22.03%
2015Memphis770.5757th (n=465)0.5343.67%
2016Memphis630.9192nd (n=489)0.5257.17%
2017Memphis540.6773rd (n=507)0.5235.97%

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

2017 Memphis 11 games, 35 catches, 521 yards, 3 TD
DateOpponentResultRecYdsTDLongRush
Aug 31vs.UL MonroeW 37–⁠29119019–
Sep 16vs.UCLAW 48–⁠45223120–
Sep 23vs.Southern IllinoisW 44–⁠31457026–
Sep 30atUCFL 13–⁠40324017–
Oct 6atUConnW 70–⁠31441015–
Oct 14vs.NavyW 30–⁠27230020–
Oct 19atHoustonW 42–⁠38563016–
Oct 27vs.TulaneW 56–⁠26356030–
Nov 3atTulsaW 41–⁠14474038–
Nov 25vs.East CarolinaW 70–⁠13249146–
Dec 30 ✦vs.Iowa StateL 20–⁠21585136–
2016 Memphis 12 games, 42 catches, 677 yards, 4 TD
DateOpponentResultRecYdsTDLongRush
Sep 3vs.Southeast Missouri StateW 35–⁠17121021–
Sep 17vs.KansasW 43–⁠7434114–
Sep 24vs.Bowling GreenW 77–⁠3372140–
Oct 1atOle MissL 28–⁠48669018–
Oct 6vs.TempleW 34–⁠27684021–
Oct 14atTulaneW 24–⁠14474028–
Oct 22atNavyL 28–⁠42343016–
Oct 29vs.TulsaL 30–⁠59124024–
Nov 12vs.South FloridaL 42–⁠49224016–
Nov 18atCincinnatiW 34–⁠7342016–
Nov 25vs.HoustonW 48–⁠446142267–
Dec 20 ✦vs.Western KentuckyL 31–⁠51348022–
2015 Memphis 13 games, 51 catches, 670 yards, 1 TD
DateOpponentResultRecYdsTDLongRush
Sep 5vs.Missouri StateW 63–⁠7116016–
Sep 12atKansasW 55–⁠23568032–
Sep 19atBowling GreenW 44–⁠41340015–
Sep 24vs.CincinnatiW 53–⁠46450018–
Oct 2atSouth FloridaW 24–⁠17469033–
Oct 17vs.Ole MissW 37–⁠24329021–
Oct 23atTulsaW 66–⁠42460026–
Oct 31vs.TulaneW 41–⁠137107029–
Nov 7vs.NavyL 20–⁠45568017–
Nov 14atHoustonL 34–⁠355430194
Nov 21atTempleL 12–⁠31551021–
Nov 28vs.SMUW 63–⁠0143143–
Dec 30 ✦vs.AuburnL 10–⁠31426011–
2014 Memphis 7 games, 15 catches, 242 yards, 2 TD
DateOpponentResultRecYdsTDLongRush
Sep 20vs.Middle TennesseeW 36–⁠17325012–
Oct 4atCincinnatiW 41–⁠14238025–
Oct 25atSMUW 48–⁠10296154–
Nov 7atTempleW 16–⁠1321109–
Nov 22vs.South FloridaW 31–⁠20116016–
Nov 29vs.UConnW 41–⁠10333121–
Dec 22 ✦vs.BYUW 55–⁠48223012–

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.