Linebacker, Iowa State, 2012–⁠16

Kane Seeley

Lettered 2013–⁠16 (school media guide)

Number
No. 29
Height
6′2″
Hometown
Perry, IA

Kane Seeley played linebacker at Iowa State (2012–⁠16).

Career highs

11tackles, career highthree times; last vs. West Virginia, 2016

Defense

SeasonTeamTklSoloTFLSacksIntPDHur
2016Iowa State784272112

Season lines from CollegeFootballData, regular season and bowls.

Defense before 2016

SeasonGSoloAstTkl
2013N11112
2014E7 of 12171734
2015E7 of 12718

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

SeasonTeamNo.PosHt
2012Iowa State29LB
2013Iowa State29LB
2014Iowa State29LB
2015Iowa State29LB
2016Iowa State29LB6′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 Iowa State 12 games, 78 tackles, 2 sacks, 1 INT
DateOpponentResultTklSoloTFLSacksIntPD
Sep 3vs.Northern IowaL 20–⁠25642100
Sep 10atIowaL 3–⁠42310.5000
Sep 17atTCUL 20–⁠41320000
Sep 24vs.San José StateW 44–⁠101130000
Oct 1vs.BaylorL 42–⁠45200000
Oct 8atOklahoma StateL 31–⁠38440000
Oct 15atTexasL 6–⁠2711100010
Oct 29vs.Kansas StateL 26–⁠31621.5000
Nov 3vs.OklahomaL 24–⁠34831100
Nov 12atKansasW 31–⁠241060000
Nov 19vs.Texas TechW 66–⁠10330000
Nov 26vs.West VirginiaL 19–⁠491142001
2015 Iowa State 1 game, 1 catch, 5 yards
DateOpponentResultTklSoloTFLSacksIntPD
Nov 28atWest VirginiaL 6–⁠30––––––

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.