Receiver, Oklahoma State, 2009–11
Colton Chelf
- Number
- No. 83
- Height
- 5′9″
- Hometown
- Enid, OK
Colton Chelf played receiver at Oklahoma State (2009–11).
Career highs
97receiving yards, career highvs. Stanford, 2011Team titles: Big 12 champions, 2011
Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2010 | Oklahoma State | 11 | 200 | 18.2 | 1 | 62 |
| 2011 | Oklahoma State | 21 | 291 | 13.9 | 0 | 39 |
| Career | 32 | 491 | 15.3 | 1 | 62 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Ht |
|---|---|---|---|---|
| 2009 | Oklahoma State | 83 | WR | |
| 2010 | Oklahoma State | 83 | WR | |
| 2011 | Oklahoma State | 83 | WR | 5′9″ |
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 Oklahoma State 8 games, 21 catches, 291 yards
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 8 | vs. | W 37–14 | 3 | 24 | 0 | 11 |
| Sep 24 | at | W 30–29 | 2 | 21 | 0 | 15 |
| Oct 8 | vs. | W 70–28 | 3 | 70 | 0 | 39 |
| Oct 29 | vs. | W 59–24 | 3 | 14 | 0 | 6 |
| Nov 5 | vs. | W 52–45 | 1 | 12 | 0 | 12 |
| Nov 12 | at | W 66–6 | 1 | 9 | 0 | 9 |
| Nov 18 | at | L 31–37 | 3 | 44 | 0 | 31 |
| Jan 2 ✦ | vs. | W 41–38 | 5 | 97 | 0 | 29 |
2010 Oklahoma State 7 games, 11 catches, 200 yards, 1 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 4 | vs. | W 65–17 | 1 | 7 | 0 | 7 |
| Sep 11 | vs. | W 41–38 | 2 | 51 | 0 | 45 |
| Sep 18 | vs. | W 65–28 | 1 | 17 | 0 | 17 |
| Sep 30 | vs. | W 38–35 | 1 | 8 | 0 | 8 |
| Oct 16 | at | W 34–17 | 1 | 3 | 0 | 3 |
| Nov 6 | vs. | W 55–28 | 3 | 79 | 1 | 62 |
| Nov 20 | at | W 48–14 | 2 | 35 | 0 | 19 |
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.
