Defensive back, Army, 2015–⁠18

Mike Reynolds

Number
No. 10
Height
5′10″
Weight
185 lb
Class (2018)
Senior
Hometown
Dothan, AL

Mike Reynolds played defensive back at Army (2015–⁠18).

Defense

Tackles, season by season, with his team’s record
SeasonTeamTklSoloTFLSacksIntPDHur
2016Army6400110
2017Army221800070
2018Army1410103110
Career4232104190

Returns

SeasonTeamPRYdsTD
2017Army9620
2018Army9980
Career181600

Season lines from CollegeFootballData, regular season and bowls. A dash: the source has no number for that season (often an FCS season), and career totals count only the numbers on file.

On the roster

SeasonTeamNo.PosClassHtWt
2015Army10DBFr.
2016Army10DBSo.
2017Army10DBJr.
2018Army10DBSr.5′10″185

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

2018 Army 9 games, 14 tackles, 3 INT
DateOpponentResultTklSacksIntPDPR
Sep 8vs.LibertyW 38–⁠1410011
Sep 22atOklahomaL 21–⁠282010–
Sep 29atBuffaloW 42–⁠133002–
Oct 13vs.San José StateW 52–⁠310012
Oct 20vs.Miami (OH)W 31–⁠3040031
Nov 3vs.Air ForceW 17–⁠1420111
Nov 10vs.LafayetteW 31–⁠13––––1
Nov 17vs.ColgateW 28–⁠14––––1
Dec 8vs.NavyW 17–⁠1010132
2017 Army 10 games, 22 tackles
DateOpponentResultTklSacksIntPDPR
Sep 1vs.FordhamW 64–⁠66000–
Sep 9vs.BuffaloW 21–⁠171001–
Sep 16atOhio StateL 7–⁠383001–
Sep 23atTulaneL 17–⁠2130022
Sep 30vs.UTEPW 35–⁠2140022
Oct 7atRiceW 49–⁠1210002
Oct 14vs.Eastern MichiganW 28–⁠271001–
Oct 21vs.TempleW 31–⁠2820002
Nov 4atAir ForceW 21–⁠01000–
Nov 18atNorth TexasL 49–⁠52––––1
2016 Army 4 games, 6 tackles, 1 INT
DateOpponentResultTklSacksIntPDPR
Sep 2atTempleW 28–⁠131010–
Sep 10vs.RiceW 31–⁠141001–
Sep 17atUTEPW 66–⁠142000–
Dec 27 ✦vs.North TexasW 38–⁠312000–

No box score in the source for Oct 8 at Duke, so that game is 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.