Defensive back, Army, 2013–⁠17

Marcus Hyatt

Number
No. 1
Height
5′10″
Weight
180 lb
Class (2017)
Senior
Hometown
Lilburn, GA

Marcus Hyatt played defensive back at Army (2013–⁠17).

Defense

SeasonTeamTklSoloTFLSacksIntPDHur
2016Army29192.50240

Returns

SeasonTeamKRYdsTD
2015Army305750

Season lines from CollegeFootballData, regular season and bowls.

Defense before 2016

SeasonGSoloAstTkl
201510 of 12213

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

SeasonTeamNo.PosClassHtWt
2013Army1DBRS
2014Army1DBFr.
2015Army1DBSo.
2016Army1DBJr.
2017Army1DBSr.5′10″180

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 Army 7 games, 29 tackles, 2 INT
DateOpponentResultTklSacksIntPDKRYds
Sep 2atTempleW 28–⁠135010––
Sep 10vs.RiceW 31–⁠142001––
Sep 17atUTEPW 66–⁠143001––
Sep 24atBuffaloL 20–⁠235000––
Oct 15vs.LafayetteW 62–⁠72010––
Oct 22vs.North TexasL 18–⁠355000––
Oct 29atWake ForestW 21–⁠137002––

No box score in the source for Oct 8 at Duke, so that game is not listed.

2015 Army 11 games, 30 returns, 575 yards
DateOpponentResultTklSacksIntPDKRYds
Sep 4vs.FordhamL 35–⁠37––––584
Sep 12atUConnL 17–⁠22––––473
Sep 19vs.Wake ForestL 14–⁠17––––117
Sep 26atEastern MichiganW 58–⁠36––––119
Oct 3atPenn StateL 14–⁠20––––485
Oct 10vs.DukeL 3–⁠44––––591
Oct 17vs.BucknellW 21–⁠14––––127
Oct 24atRiceL 31–⁠38––––239
Nov 14vs.TulaneL 31–⁠34––––361
Nov 21vs.RutgersL 21–⁠31––––243
Dec 12vs.NavyL 17–⁠21––––236

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.