Running back, Georgia Tech, 2010–⁠14

B.J. Bostic

Number
No. 7
Height
5′11″
Hometown
Louisville, GA

B.J. Bostic played running back at Georgia Tech (2010–⁠14).

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2010Georgia Tech131279.8043
2012Georgia Tech342126.2017
2013Georgia Tech161167.3030
2014Georgia Tech221346.1119
Career855896.9143

Returns

SeasonTeamKRYdsTD
2010Georgia Tech285740

Receiving

SeasonTeamRecYdsAvgTDLong
2012Georgia Tech713919.9039
2013Georgia Tech5336.6010
2014Georgia Tech23718.5024
Career1420914.9039

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHt
2010Georgia Tech7RB
2011Georgia Tech7RB
2012Georgia Tech7RB
2013Georgia Tech7RB
2014Georgia Tech7RB5′11″

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.

Per play

SeasonTeamPlaysEPA/playPctileMedianTotalUsage
2013Georgia Tech220.25––5.53%
2014Georgia Tech280.41––11.54%

Expected points added: how much the player’s plays moved the team’s expected score, per play and in total. Plays: total EPA divided by EPA per play, the plays the source credits to him (for a receiver roughly his catches and runs, not every target; for a passer, not every attempt), so it can differ from attempts plus carries. Percentile: against the position’s regulars that season across all divisions on file (quarterbacks with 150+ plays, backs 60+, receivers and tight ends 30+), with how many there were (n) and their median; a dash means too few plays to rank. A season in progress uses the full-season bar scaled by games played, never below 75 plays for quarterbacks, 30 for backs and 20 for receivers. The cohort grows or shrinks with the source’s coverage each season (2025 lists far more players), so compare percentiles rather than raw EPA across years. FCS seasons are marked. Usage: the share of the team’s plays the player was part of (shown from 20 plays). From CollegeFootballData, 2013 on.

Game by game

2014 Georgia Tech 11 games, 134 rushing yards, 1 TD
DateOpponentResultCarRush ydsRush TDKRYds
Aug 30vs.WoffordW 38–⁠193170––
Sep 6atTulaneW 38–⁠214130––
Sep 13vs.Georgia SouthernW 42–⁠382160––
Sep 20atVirginia TechW 27–⁠241−20––
Oct 4vs.MiamiW 28–⁠172211––
Oct 11vs.DukeL 25–⁠312220––
Oct 25atPittsburghW 56–⁠28160––
Nov 8atNC StateW 56–⁠232200––
Nov 15vs.ClemsonW 28–⁠61−10––
Dec 6vs.Florida StateL 35–⁠37270––
Dec 31 ✦vs.Mississippi StateW 49–⁠342150––
2013 Georgia Tech 10 games, 116 rushing yards
DateOpponentResultCarRush ydsRush TDKRYds
Aug 31vs.ElonW 70–⁠02200––
Sep 14atDukeW 38–⁠143270––
Sep 21vs.North CarolinaW 28–⁠20440––
Sep 26vs.Virginia TechL 10–⁠171100––
Oct 5atMiamiL 30–⁠45150––
Oct 19vs.SyracuseW 56–⁠01−20––
Oct 26atVirginiaW 35–⁠25160––
Nov 14atClemsonL 31–⁠550300––
Nov 23vs.Alabama A&MW 66–⁠72150––
Nov 30vs.GeorgiaL 34–⁠41110––
2012 Georgia Tech 11 games, 212 rushing yards
DateOpponentResultCarRush ydsRush TDKRYds
Sep 3atVirginia TechL 17–⁠205350––
Sep 8vs.PresbyterianW 59–⁠31150––
Sep 15vs.VirginiaW 56–⁠204300––
Sep 22vs.MiamiL 36–⁠422150––
Oct 20vs.Boston CollegeW 37–⁠175280––
Oct 27vs.BYUL 17–⁠412−10––
Nov 3atMarylandW 33–⁠132130––
Nov 10atNorth CarolinaW 68–⁠50150––
Nov 24atGeorgiaL 10–⁠425330––
Dec 1vs.Florida StateL 15–⁠215250––
Dec 31 ✦vs.USCW 21–⁠72140––
2010 Georgia Tech 12 games, 28 returns, 574 yards
DateOpponentResultCarRush ydsRush TDKRYds
Sep 4vs.South Carolina StateW 41–⁠105300––
Sep 18atNorth CarolinaW 30–⁠24–––118
Sep 25vs.NC StateL 28–⁠452510135
Oct 2atWake ForestW 24–⁠203410369
Oct 9vs.VirginiaW 33–⁠21–––124
Oct 16vs.Middle TennesseeW 42–⁠14350––
Oct 23atClemsonL 13–⁠27–––5101
Nov 4atVirginia TechL 21–⁠28–––246
Nov 13vs.MiamiL 10–⁠35–––6125
Nov 20vs.DukeW 30–⁠20–––249
Nov 27atGeorgiaL 34–⁠42–––698
Dec 27 ✦vs.Air ForceL 7–⁠14–––19

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.