Running back, Georgia Tech, 2011–⁠15

Broderick Snoddy

Number
No. 22
Height
5′9″
Hometown
Carrollton, GA

Broderick Snoddy played running back at Georgia Tech (2011–⁠15).

Career highs

82rushing yards, career highat Pittsburgh, 20143rushing touchdowns, career highat Pittsburgh, 2014

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2012Georgia Tech13503.8119
2013Georgia Tech241506.3027
2014Georgia Tech2828310.1346
2015Georgia Tech201819.1148
Career856647.8548

Returns

SeasonTeamKRYdsTD
2012Georgia Tech2570
2013Georgia Tech2290
2014Georgia Tech51120
Career91980

Season lines from CollegeFootballData, regular season and bowls.

Defense before 2016

SeasonGSoloAstTkl
20128819
2013N12101
On file9110

Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources, marked by season: unmarked, cfbstats.com (Open Data Commons Attribution License), its game lines summed (G: the games he has a line in); N, NCAA statistics, via octonion/football, the season’s official lines (G: games played). A dash: the source has no number for it.

On the roster

SeasonTeamNo.PosHt
2011Georgia Tech22RB
2012Georgia Tech22RB
2013Georgia Tech22RB
2014Georgia Tech22RB
2015Georgia Tech22RB5′9″

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 Tech230.32––7.48%
2014Georgia Tech310.91––28.36%
2015Georgia Tech210.20––4.25%

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

2015 Georgia Tech 6 games, 181 rushing yards, 1 TD
DateOpponentResultCarRush ydsRush TDKRYds
Sep 3vs.Alcorn StateW 69–⁠63510––
Sep 12vs.TulaneW 65–⁠104350––
Sep 19atNotre DameL 22–⁠307770––
Sep 26atDukeL 20–⁠342120––
Nov 12vs.Virginia TechL 21–⁠23310––
Nov 21atMiamiL 21–⁠38151––
2014 Georgia Tech 9 games, 283 rushing yards, 3 TD
DateOpponentResultCarRush ydsRush TDKRYds
Aug 30vs.WoffordW 38–⁠19190––
Sep 6atTulaneW 38–⁠212130118
Sep 13vs.Georgia SouthernW 42–⁠38–––239
Sep 20atVirginia TechW 27–⁠24–––129
Oct 18atNorth CarolinaL 43–⁠485390126
Oct 25atPittsburghW 56–⁠286823––
Nov 1vs.VirginiaW 35–⁠107520––
Nov 8atNC StateW 56–⁠235370––
Nov 15vs.ClemsonW 28–⁠62510––
2013 Georgia Tech 6 games, 150 rushing yards
DateOpponentResultCarRush ydsRush TDKRYds
Aug 31vs.ElonW 70–⁠08450––
Sep 14atDukeW 38–⁠143290––
Sep 26vs.Virginia TechL 10–⁠17–––229
Oct 12atBYUL 20–⁠38270––
Oct 19vs.SyracuseW 56–⁠0200––
Nov 23vs.Alabama A&MW 66–⁠79690––
2012 Georgia Tech 6 games, 50 rushing yards, 1 TD
DateOpponentResultCarRush ydsRush TDKRYds
Sep 8vs.PresbyterianW 59–⁠36131––
Sep 15vs.VirginiaW 56–⁠203230––
Sep 29vs.Middle TennesseeL 28–⁠49–––257
Oct 27vs.BYUL 17–⁠41100––
Nov 3atMarylandW 33–⁠132110––
Nov 24atGeorgiaL 10–⁠42130––

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.