Defensive line, Eastern Michigan, 2012–⁠16

Mike Brown

Number
No. 96
Height
6′2″
Hometown
Sandusky, OH

Mike Brown played defensive line at Eastern Michigan (2012–⁠16).

Career highs

8tackles, career highvs. Miami (OH), 2016

Defense

SeasonTeamTklSoloTFLSacksPDHur
2016Eastern Michigan2632020

Season lines from CollegeFootballData, regular season and bowls.

Defense before 2016

SeasonGSoloAstTkl
20121011
2013N4101
2014E9 of 1162026
2015E10 of 12162844

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); 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
2012Eastern Michigan96DL
2013Eastern Michigan96DL
2014Eastern Michigan96DL
2015Eastern Michigan96DL
2016Eastern Michigan96DL6′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 Eastern Michigan 11 games, 26 tackles
DateOpponentResultTklSoloTFLSacksPD
Sep 2vs.Mississippi Valley StateW 61–⁠14100.500
Sep 10atMissouriL 21–⁠6111000
Sep 23vs.WyomingW 27–⁠2410000
Oct 1atBowling GreenW 28–⁠2510002
Oct 8vs.ToledoL 20–⁠35100.500
Oct 15atOhioW 27–⁠2010000
Oct 22atWestern MichiganL 31–⁠4511000
Oct 29vs.Miami (OH)L 15–⁠2880000
Nov 8atBall StateW 48–⁠41400.500
Nov 16vs.Northern IllinoisL 24–⁠31510.500
Nov 22vs.Central MichiganW 26–⁠2120000

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.