Receiver, Kansas State, 2008–⁠10

Aubrey Quarles

Number
No. 89
Height
5′11″
Hometown
Aurora, CO

Aubrey Quarles played receiver at Kansas State (2008–⁠10).

Career highs

9catches, career hightwice; last at Missouri, 2010133receiving yards, career highat Missouri, 2010

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2008*Kansas State3440712.0136
2010Kansas State5176014.9567
Career851,16713.7667

Returns

SeasonTeamKRYdsTD
2010Kansas State184591

Season lines from CollegeFootballData, regular season and bowls. * That team-season’s player lines are missing part of the team’s yards in our source, so these numbers may be short.

On the roster

SeasonTeamNo.PosHt
2008Kansas State89WR
2009Kansas State89WR
2010Kansas State89WR5′11″

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.

Game by game

2010 Kansas State 12 games, 51 catches, 760 yards, 5 TD
DateOpponentResultRecRec ydsRec TDKRYds
Sep 4vs.UCLAW 31–⁠221130123
Sep 11vs.Missouri StateW 48–⁠247821––
Sep 18vs.Iowa StateW 27–⁠201110––
Sep 25vs.UCFW 17–⁠131581116
Oct 7vs.NebraskaL 13–⁠485570––
Oct 14atKansasW 59–⁠73230122
Oct 23atBaylorL 42–⁠4761311240
Oct 30vs.Oklahoma StateL 14–⁠248540235
Nov 13atMissouriL 28–⁠3891331236
Nov 20atColoradoL 36–⁠4451141119
Nov 27atNorth TexasW 49–⁠411905197
Dec 30 ✦vs.SyracuseL 34–⁠364750371
2008 Kansas State 9 games, 34 catches, 407 yards, 1 TD
DateOpponentResultRecRec ydsRec TDKRYds
Aug 30vs.North TexasW 45–⁠66570––
Sep 6vs.Montana StateW 69–⁠102521––
Sep 17atLouisvilleL 29–⁠383280––
Sep 27vs.LouisianaW 45–⁠376620––
Oct 4vs.Texas TechL 28–⁠582210––
Oct 11atTexas A&MW 44–⁠3091020––
Oct 18atColoradoL 13–⁠142110––
Nov 1atKansasL 21–⁠523450––
Nov 8atMissouriL 24–⁠411290––

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.