Defensive back, Central Michigan, 2012–16
Colton Odykirk
- Number
- No. 34
- Height
- 6′2″
- Hometown
- Mount Pleasant, MI
Colton Odykirk played defensive back at Central Michigan (2012–16).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2016 | Central Michigan | 8 | 6 | 0 | 0 | 0 | 2 |
Season lines from CollegeFootballData, regular season and bowls.
Defense before 2016
| Season | G | Solo | Ast | Tkl |
|---|---|---|---|---|
| 2013N | 6 | 1 | 2 | 3 |
| 2014E | 10 of 13 | 0 | 1 | 1 |
Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources, marked by season: N, NCAA statistics, via octonion/football, the season’s official lines (G: games played); E, ESPN play-by-play participants, via SportsDataverse: tackles only, counted in the games whose play-by-play names tacklers (G: those games, of his team’s), so part of the season, not its total. A dash: the source has no number for it.
On the roster
| Season | Team | No. | Pos | Ht |
|---|---|---|---|---|
| 2012 | Central Michigan | 34 | DB | |
| 2013 | Central Michigan | 34 | DB | |
| 2014 | Central Michigan | 34 | DB | |
| 2015 | Central Michigan | 34 | DB | |
| 2016 | Central Michigan | 34 | DB | 6′2″ |
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
2016 Central Michigan 5 games, 8 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 1 | vs. Presbyterian | W 49–3 | 2 | 2 | 0 | 0 | 0 |
| Sep 17 | vs. UNLV | W 44–21 | 0 | 0 | 0 | 0 | 0 |
| Oct 22 | at Toledo | L 17–31 | 1 | 1 | 0 | 0 | 0 |
| Nov 15 | vs. Ohio | W 27–20 | 4 | 2 | 0 | 0 | 0 |
| Dec 19 ✦ | vs. Tulsa | L 10–55 | 1 | 1 | 0 | 0 | 0 |
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.