Receiver, Northern Arizona (from Washington), 2012–⁠16

Kendyl Taylor

Number
No. 13
Height
5′10″
Hometown
Chandler, AZ

Kendyl Taylor played receiver at Washington (2012–⁠14) and Northern Arizona (2015–⁠16).

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2012Washington141107.9123
2014Washington181468.1228
2016Northern Arizona221.003
Career342587.6328

Rushing

SeasonTeamCarYdsAvgTDLong
2012Washington352096.0044
2014Washington221.003
2015Northern Arizona591.805
2016Northern Arizona19432.3010
Career612634.3044

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHt
2012Washington13WR
2013Washington13WR
2014Washington13WR
2015Northern Arizona13WR
2016Northern Arizona13WR5′10″

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
2014Washington210.40––8.43%
2015Northern Arizona (FCS)6-0.47––-2.8–
2016Northern Arizona (FCS)22-0.44––-9.732%

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 Northern Arizona 1 game, 2 catches, 2 yards
DateOpponentResultRecYdsTDLongRush
Sep 3atArizona StateL 13–⁠44220343

No box score in the source for Sep 10 at Western Illinois; Sep 17 vs. New Mexico Highlands; Sep 24 vs. Eastern Washington; Oct 1 at Northern Colorado; Oct 8 at Montana State; Oct 15 vs. Idaho State; Oct 22 vs. Montana; Nov 5 at Weber State; Nov 12 at North Dakota; Nov 19 vs. Southern Utah, so those games are not listed.

2015 Northern Arizona 1 game, 2 returns, 39 yards
DateOpponentResultRecYdsTDLongRush
Sep 19atArizonaL 13–⁠77––––9

No box score in the source for Sep 5 at Stephen F. Austin; Sep 12 vs. New Mexico Highlands; Sep 26 at Montana; Oct 3 vs. Montana State; Oct 10 at UC Davis; Oct 24 vs. Weber State; Oct 31 vs. Northern Colorado; Nov 7 at Eastern Washington; Nov 14 vs. Sacramento State; Nov 21 at Southern Utah, so those games are not listed.

2014 Washington 10 games, 18 catches, 146 yards, 2 TD
DateOpponentResultRecYdsTDLongRush
Aug 30atHawai’iW 17–⁠161404–
Sep 13vs.IllinoisW 44–⁠191404–
Sep 20vs.Georgia StateW 45–⁠14211110–
Oct 11atCaliforniaW 31–⁠7119019–
Oct 25vs.Arizona StateL 10–⁠24330018–
Nov 1atColoradoW 38–⁠2319193
Nov 8vs.UCLAL 30–⁠4421208–
Nov 15atArizonaL 26–⁠27128028–
Nov 29atWashington StateW 31–⁠13518011−1
Jan 2 ✦vs.Oklahoma StateL 22–⁠30111011–
2012 Washington 11 games, 14 catches, 110 yards, 1 TD
DateOpponentResultRecYdsTDLongRush
Sep 1vs.San Diego StateW 21–⁠121606–
Sep 27vs.StanfordW 17–⁠131110119
Oct 6atOregonL 21–⁠523170929
Oct 13vs.USCL 14–⁠24––––11
Oct 20atArizonaL 17–⁠523130947
Oct 27vs.Oregon StateW 20–⁠172120811
Nov 2atCaliforniaW 21–⁠1311001015
Nov 10vs.UtahW 34–⁠1517076
Nov 17atColoradoW 38–⁠312312378
Nov 23atWashington StateL 28–⁠311110111
Dec 22 ✦vs.Boise StateL 26–⁠28––––2

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.