Cornerback, Indiana, 2009–13
Nick Turner
- Number
- No. 39
- Height
- 6′0″
- Hometown
- Indianapolis, IN
Nick Turner played cornerback at Indiana (2009–13).
Career highs
103rushing yards, career highat Wisconsin, 2010Returns
| Season | Team | KR | Yds | TD |
|---|---|---|---|---|
| 2010 | Indiana | 12 | 253 | 0 |
Rushing
Season lines from CollegeFootballData, regular season and bowls.
Defense before 2016
| Season | G | Solo | Ast | Tkl |
|---|---|---|---|---|
| 2010 | 11 | 1 | 0 | 1 |
| 2011 | 2 | 0 | 1 | 1 |
| On file | 1 | 1 | 2 | |
Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources: cfbstats.com (Open Data Commons Attribution License), its game lines summed (G: the games he has a line in). A dash: the source has no number for it.
On the roster
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
2011 Indiana 1 game, −3 rushing yards
| Date | Opponent | Result | KR | Yds | TD |
|---|---|---|---|---|---|
| Oct 1 | vs. Penn State | L 10–16 | – | – | – |
2010 Indiana 11 games, 12 returns, 253 yards
| Date | Opponent | Result | KR | Yds | TD |
|---|---|---|---|---|---|
| Sep 2 | vs. Towson | W 51–17 | 2 | 72 | 0 |
| Sep 18 | at Western Kentucky | W 38–21 | – | – | – |
| Sep 25 | vs. Akron | W 35–20 | 1 | 12 | 0 |
| Oct 2 | vs. Michigan | L 35–42 | 1 | 19 | 0 |
| Oct 9 | at Ohio State | L 10–38 | 1 | 18 | 0 |
| Oct 16 | vs. Arkansas State | W 36–34 | – | – | – |
| Oct 30 | vs. Northwestern | L 17–20 | – | – | – |
| Nov 6 | vs. Iowa | L 13–18 | 1 | 28 | 0 |
| Nov 13 | at Wisconsin | L 20–83 | 3 | 50 | 0 |
| Nov 20 | vs.Penn State | L 24–41 | 3 | 54 | 0 |
| Nov 27 | at Purdue | W 34–31 | – | – | – |
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.