Defensive tackle, Kansas State, 2013–16
Matt Seiwert
Lettered 2015–16 (school media guide)
- Number
- No. 92
- Height
- 6′3″
- Hometown
- Conway Springs, KS
Matt Seiwert played defensive tackle at Kansas State (2013–16).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | Int | PD | Hur |
|---|---|---|---|---|---|---|---|---|
| 2016 | Kansas State | 8 | 4 | 0 | 0 | 1 | 1 | 0 |
Season lines from CollegeFootballData, regular season and bowls.
Defense before 2016
| Season | G | Solo | Ast | Tkl |
|---|---|---|---|---|
| 2015 | 8 of 13 | 2 | 1 | 3 |
Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources: 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 |
|---|---|---|---|---|
| 2013 | Kansas State | 92 | DT | |
| 2014 | Kansas State | 92 | DT | |
| 2015 | Kansas State | 92 | DT | |
| 2016 | Kansas State | 92 | DT | 6′3″ |
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 Kansas State 7 games, 8 tackles, 1 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 17 | vs. Florida Atlantic | W 63–7 | 2 | 2 | 0 | 0 | 0 | 0 |
| Sep 24 | vs. Missouri State | W 35–0 | 1 | 1 | 0 | 0 | 1 | 0 |
| Oct 22 | vs. Texas | W 24–21 | 1 | 0 | 0 | 0 | 0 | 0 |
| Oct 29 | at Iowa State | W 31–26 | 2 | 1 | 0 | 0 | 0 | 0 |
| Nov 19 | at Baylor | W 42–21 | 1 | 0 | 0 | 0 | 0 | 0 |
| Nov 26 | vs. Kansas | W 34–19 | 0 | 0 | 0 | 0 | 0 | 1 |
| Dec 3 | at TCU | W 30–6 | 1 | 0 | 0 | 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.