Cornerback, Georgia State, 2014–⁠17

B.J. Clay

Number
No. 29
Height
6′0″
Weight
190 lb
Hometown
Dacula, GA

B.J. Clay played cornerback at Georgia State (2014–⁠17).

Career highs

2interceptions, career highvs. UT Martin, 2016

Defense

Tackles, season by season, with his team’s record
SeasonTeamTklSoloTFLSacksIntPDHur
2016Georgia State10500350
2017Georgia State7500030
Career171000380

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.

Defense before 2016

SeasonGSoloAstTkl
201410 of 1213417
201510 of 13505

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
2014Georgia State29CB
2015Georgia State29CB
2016Georgia State29CB
2017Georgia State29CB6′0″190

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 Georgia State 5 games, 7 tackles
DateOpponentResultTklSoloTFLSacksIntPD
Oct 14atUL MonroeW 47–⁠37110000
Oct 21vs.TroyL 10–⁠34110001
Oct 26vs.South AlabamaW 21–⁠13310002
Nov 25vs.App StateL 10–⁠31110000
Dec 2vs.IdahoL 10–⁠24110000
2016 Georgia State 7 games, 10 tackles, 3 INT
DateOpponentResultTklSoloTFLSacksIntPD
Sep 2vs.Ball StateL 21–⁠31100000
Sep 10atAir ForceL 14–⁠48100000
Oct 1atApp StateL 3–⁠17000001
Oct 22vs.UT MartinW 31–⁠6330023
Oct 29atSouth AlabamaL 10–⁠13310011
Nov 3vs.Arkansas StateL 16–⁠31110000
Nov 19vs.Georgia SouthernW 30–⁠24100000

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.