Defensive back, Air Force, 2015–⁠17

Marquis Griffin

Number
No. 2
Height
5′11″
Weight
195 lb
Hometown
Stockbridge, GA

Marquis Griffin played defensive back at Air Force (2015–⁠17).

Career highs

11tackles, career hightwice; last vs. Army, 2017

Defense

Tackles, season by season, with his team’s record
SeasonTeamTklSoloTFLSacksPDHur
2016Air Force22170.5010
2017Air Force62413.5060
Career84584070

Season lines from CollegeFootballData, regular season and bowls.

Defense before 2016

SeasonGSoloAstTkl
201510 of 14437

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.PosHtWt
2015Air Force2DB
2016Air Force2DB
2017Air Force2DB5′11″195

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

2017 Air Force 11 games, 62 tackles
DateOpponentResultTklSoloTFLSacksPD
Sep 2vs.VMIW 62–⁠053101
Sep 16atMichiganL 13–⁠291190.501
Sep 23vs.San Diego StateL 24–⁠2873001
Sep 30atNew MexicoL 38–⁠5644100
Oct 7atNavyL 45–⁠4852000
Oct 14vs.UNLVW 34–⁠3022001
Oct 20atNevadaW 45–⁠4243002
Oct 28atColorado StateW 45–⁠2876000
Nov 4vs.ArmyL 0–⁠21114100
Nov 18atBoise StateL 19–⁠4455000
Nov 25vs.Utah StateW 38–⁠3510000
2016 Air Force 7 games, 22 tackles
DateOpponentResultTklSoloTFLSacksPD
Sep 3vs.Abilene ChristianW 37–⁠2131000
Sep 10vs.Georgia StateW 48–⁠1411000
Sep 24atUtah StateW 27–⁠2066000
Oct 1vs.NavyW 28–⁠1411000
Oct 8atWyomingL 26–⁠3542000
Oct 22vs.Hawai’iL 27–⁠3422000
Oct 28atFresno StateW 31–⁠21540.501

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.