Receiver, Iowa State, 2009–⁠12

Jerome Tiller

Number
No. 11
Height
6′3″
Hometown
San Antonio, TX

Jerome Tiller played receiver at Iowa State (2009–⁠12).

Career highs

155passing yards, career hightwice; last vs. Missouri, 2010

Receiving

SeasonTeamRecYdsAvgTDLong
2012Iowa State181749.7120

Rushing

SeasonTeamCarYdsAvgTDLong
2009Iowa State442164.9220
2010Iowa State42661.6021
Career862823.3221

Passing

SeasonTeamCmpAttPctYdsY/ATDInt
2009Iowa State417356.23765.214
2010Iowa State398247.63634.410
2012Iowa State010.000.000
Career8015651.37394.724

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHt
2009Iowa State11WR
2010Iowa State11WR
2011Iowa State11WR
2012Iowa State11WR6′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.

Game by game

2012 Iowa State 9 games, 18 catches, 174 yards, 1 TD
DateOpponentResultRecYdsTDLongRush
Sep 1vs.TulsaW 38–⁠23217012–
Sep 8atIowaW 9–⁠6333014–
Sep 15vs.Western IllinoisW 37–⁠3441020–
Oct 20atOklahoma StateL 10–⁠311909–
Oct 27vs.BaylorW 35–⁠2121007–
Nov 10atTexasL 7–⁠33218011–
Nov 17atKansasW 51–⁠23110010–
Nov 23vs.West VirginiaL 24–⁠31220112–
Dec 31 ✦vs.TulsaL 17–⁠31116016–
2010 Iowa State 5 games, 363 passing yards, 1 TD
DateOpponentResultRecYdsTDLongRush
Sep 18vs.Kansas StateL 20–⁠27––––10
Sep 25vs.Northern IowaW 27–⁠0––––−1
Oct 16atOklahomaL 0–⁠52––––5
Nov 13atColoradoL 14–⁠34––––−2
Nov 20vs.MissouriL 0–⁠14––––54
2009 Iowa State 7 games, 376 passing yards, 1 TD
DateOpponentResultRecYdsTDLongRush
Sep 3vs.North Dakota StateW 34–⁠17–––––
Sep 12vs.IowaL 3–⁠35––––27
Sep 19atKent StateW 34–⁠14––––7
Oct 17vs.BaylorW 24–⁠10––––74
Oct 24atNebraskaW 9–⁠7––––65
Oct 31atTexas A&ML 10–⁠35––––43
Nov 7vs.Oklahoma StateL 8–⁠34–––––

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.