Receiver, Indiana, 2011–⁠14

Nick Stoner

Number
No. 14
Height
6′1″
Hometown
Greenwood, IN

Nick Stoner played receiver at Indiana (2011–⁠14).

Career highs

6catches, career highat Bowling Green, 2014

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2012Indiana131189.1015
2013Indiana1222618.8144
2014Indiana222179.9147
Career4756111.9247

Returns

SeasonTeamKRYdsTDPRYdsTD
2011Indiana612007100
2012Indiana–––13490
Career6120020590

Season lines from CollegeFootballData, regular season and bowls. A dash: the source has no number for that season (often an FCS season), and career totals count only the numbers on file.

Defense before 2016

SeasonGSoloAstTkl
20117516
201211202
2013N12314
On file10212

Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources, marked by season: unmarked, cfbstats.com (Open Data Commons Attribution License), its game lines summed (G: the games he has a line in); N, NCAA statistics, via octonion/football, the season’s official lines (G: games played). A dash: the source has no number for it.

On the roster

SeasonTeamNo.PosHt
2011Indiana14WR
2012Indiana14WR
2013Indiana14WR
2014Indiana14WR6′1″

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
2013Indiana121.24––14.9–
2014Indiana280.35––9.86%

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 Indiana 8 games, 22 catches, 217 yards, 1 TD
DateOpponentResultRecRec ydsRec TDKRYdsPR
Aug 30vs.Indiana StateW 28–⁠10190–––
Sep 13atBowling GreenL 42–⁠456590–––
Sep 20atMissouriW 31–⁠272560–––
Sep 27vs.MarylandL 15–⁠374400–––
Oct 4vs.North TexasW 49–⁠24330–––
Oct 11atIowaL 29–⁠451131–––
Oct 18vs.Michigan StateL 17–⁠561−30–––
Nov 29vs.PurdueW 23–⁠164400–––
2013 Indiana 7 games, 12 catches, 226 yards, 1 TD
DateOpponentResultRecRec ydsRec TDKRYdsPR
Aug 29vs.Indiana StateW 73–⁠351441–––
Sep 7vs.NavyL 35–⁠412140–––
Sep 14vs.Bowling GreenW 42–⁠102400–––
Sep 21vs.MissouriL 28–⁠453580–––
Oct 5vs.Penn StateW 44–⁠241110–––
Oct 12atMichigan StateL 28–⁠421120–––
Oct 19atMichiganL 47–⁠632470–––
2012 Indiana 11 games, 13 catches, 118 yards
DateOpponentResultRecRec ydsRec TDKRYdsPR
Sep 1vs.Indiana StateW 24–⁠172160–––
Sep 8atMassachusettsW 45–⁠6–––––2
Sep 15vs.Ball StateL 39–⁠414260––1
Sep 29atNorthwesternL 29–⁠44–––––1
Oct 6vs.Michigan StateL 27–⁠31190––3
Oct 20atNavyL 30–⁠312190–––
Oct 27atIllinoisW 31–⁠171150––1
Nov 3vs.IowaW 24–⁠21–––––1
Nov 10vs.WisconsinL 14–⁠621130––2
Nov 17atPenn StateL 22–⁠452200––1
Nov 24atPurdueL 35–⁠56–––––1
2011 Indiana 4 games, 13 returns, 130 yards
DateOpponentResultRecRec ydsRec TDKRYdsPR
Oct 15atWisconsinL 7–⁠59–––––4
Nov 5atOhio StateL 20–⁠34–––2431
Nov 19atMichigan StateL 3–⁠55–––4771
Nov 26vs.PurdueL 25–⁠33–––––1

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.