Safety, Oregon State, 2011–13
Micah Audiss
- Number
- No. 37
- Height
- 6′1″
- Hometown
- Roseburg, OR
Micah Audiss played safety at Oregon State (2011–13).
Defense
| Season | Team | Int |
|---|---|---|
| 2012 | Oregon State | 1 |
Season lines from CollegeFootballData, regular season and bowls. Before 2016 our source records only interceptions for most defenders (no tackles, tackles for loss or sacks), so these lines count interceptions only. His tackles, tackles for loss and sacks from other sources are under “Defense before 2016” below.
Defense before 2016
| Season | G | Solo | Ast | Tkl | Int |
|---|---|---|---|---|---|
| 2012 | 1 | 1 | 1 | 2 | 1 |
| 2013N | 13 | 1 | 2 | 3 | 0 |
| On file | 2 | 3 | 5 | 1 | |
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
| Season | Team | No. | Pos | Ht |
|---|---|---|---|---|
| 2011 | Oregon State | 37 | S | |
| 2012 | Oregon State | 37 | S | |
| 2013 | Oregon State | 37 | S | 6′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.
Game by game
2012 Oregon State 1 game with an interception on file, 1 INT
| Date | Opponent | Result | Int |
|---|---|---|---|
| Dec 1 | vs. Nicholls | W 77–3 | 1 |
Box scores from CollegeFootballData, 2004 on. ✦ postseason; ★ a career high on file. Before 2016 our source’s box scores record only interceptions for defenders (no tackles, tackles for loss or sacks), so only those games are listed. His tackles, tackles for loss and sacks from other sources are under “Defense before 2016” below.
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.