Receiver, Washington State, 2011–⁠14

Isiah Myers

Number
No. 88
Height
6′0″
Hometown
Orlando, FL

Isiah Myers played receiver at Washington State (2011–⁠14).

At a glance

Best season
972
Receiving yards, 2014 (Washington State, 3–⁠9)
Best game
227 yards
Vs. Portland State, week 3, 2014: No. 1 receiving game in FBS that week

Career highs

11catches, career highvs. Portland State, 2014227receiving yards, career highvs. Portland State, 20143receiving touchdowns, career highvs. Portland State, 2014

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2011Washington State77610.9025
2012Washington State4243810.4436
2013Washington State3742511.5339
2014Washington State7897212.51267
Career1641,91111.71967

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHt
2011Washington State88WR
2012Washington State88WR
2013Washington State88WR
2014Washington State88WR6′0″

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
2013Washington State350.8150th (n=341)0.8128.34%
2014Washington State1110.6266th (n=496)0.5268.811%

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

2014 Washington State 12 games, 78 catches, 972 yards, 12 TD
DateOpponentResultRecYdsTDLong
Aug 28vs.RutgersL 38–⁠41694243
Sep 5atNevadaL 13–⁠249102024
Sep 13vs.Portland StateW 59–⁠2111227367
Sep 20vs.OregonL 31–⁠3862808
Sep 27atUtahW 28–⁠27427011
Oct 4vs.CaliforniaL 59–⁠60996216
Oct 10atStanfordL 17–⁠34853013
Oct 25vs.ArizonaL 37–⁠59695237
Nov 1vs.USCL 17–⁠44220112
Nov 8atOregon StateW 39–⁠32753120
Nov 22atArizona StateL 31–⁠527111150
Nov 29vs.WashingtonL 13–⁠31366024
2013 Washington State 12 games, 37 catches, 425 yards, 3 TD
DateOpponentResultRecYdsTDLong
Aug 31atAuburnL 24–⁠31215010
Sep 7atUSCW 10–⁠7218011
Sep 14vs.Southern UtahW 48–⁠10445117
Sep 21vs.IdahoW 42–⁠0218015
Sep 28vs.StanfordL 17–⁠551707
Oct 5atCaliforniaW 44–⁠22130030
Oct 19atOregonL 38–⁠62572039
Oct 31vs.Arizona StateL 21–⁠55330021
Nov 16atArizonaW 24–⁠17338125
Nov 23vs.UtahW 49–⁠37783026
Nov 29atWashingtonL 17–⁠27424011
Dec 21 ✦vs.Colorado StateL 45–⁠48345122
2012 Washington State 9 games, 42 catches, 438 yards, 4 TD
DateOpponentResultRecYdsTDLong
Aug 30atBYUL 6–⁠30550011
Sep 8vs.Eastern WashingtonW 24–⁠20658217
Sep 14atUNLVW 35–⁠27665120
Sep 22vs.ColoradoL 34–⁠35762115
Sep 29vs.OregonL 26–⁠5121206
Oct 6atOregon StateL 6–⁠19325012
Oct 13vs.CaliforniaL 17–⁠318108036
Nov 17atArizona StateL 7–⁠46111011
Nov 23vs.WashingtonW 31–⁠28447029
2011 Washington State 4 games, 7 catches, 76 yards
DateOpponentResultRecYdsTDLong
Sep 3vs.Idaho StateW 64–⁠21216013
Sep 10vs.UNLVW 59–⁠7235025
Oct 15vs.StanfordL 14–⁠4421207
Oct 22vs.Oregon StateL 21–⁠44113013

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.