Defensive tackle, Montana State, 2016–17
Tucker Yates
- Number
- No. 92
- Height
- 6′0″
- Weight
- 310 lb
- Hometown
- Spring Branch, TX
Tucker Yates played defensive tackle at Montana State (2016–17).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2016 | Montana State | 1 | 1 | 0 | 0 | 0 | 0 |
| 2017 | Montana State | 1 | 1 | 0 | 0 | 0 | 0 |
| Career | 2 | 2 | 0 | 0 | 0 | 0 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Ht | Wt |
|---|---|---|---|---|---|
| 2016 | Montana State | 92 | DT | ||
| 2017 | Montana State | 92 | DT | 6′0″ | 310 |
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
2017 Montana State 1 game, 1 tackle
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 2 | at Washington State | L 0–31 | 1 | 1 | 0 | 0 | 0 |
No box score in the source for Sep 10 vs. South Dakota State; Sep 23 at North Dakota; Sep 30 vs. Weber State; Oct 7 vs. Portland State; Oct 14 at Eastern Washington; Oct 21 at Northern Colorado; Oct 28 vs. Idaho State; Nov 4 vs. Kennesaw State; Nov 12 at Northern Arizona; Nov 18 vs. Montana, so those games are not listed.
2016 Montana State 1 game, 1 tackle
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 1 | at Idaho | L 17–20 | 1 | 1 | 0 | 0 | 0 |
No box score in the source for Sep 10 vs. Bryant; Sep 17 vs. Western Oregon; Sep 24 vs. North Dakota; Oct 2 at Sacramento State; Oct 8 vs. Northern Arizona; Oct 15 at Weber State; Oct 22 vs. Eastern Washington; Nov 5 at Southern Utah; Nov 12 vs. UC Davis; Nov 19 at Montana, so those games are not listed.
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.