Running back, Georgia Tech, 2009–⁠13

David Sims

Number
No. 20
Height
6′0″
Hometown
St. Matthews, SC

David Sims played running back at Georgia Tech (2009–⁠13).

Career highs

111rushing yards, career highvs. Alabama A&M, 20132rushing touchdowns, career highfive times; last at Virginia, 2013

Team titles: ACC champions, 2009

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2010Georgia Tech7588.3120
2011Georgia Tech1356985.2741
2012Georgia Tech1356124.5419
2013Georgia Tech1618845.51139
Career4382,2525.12341

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHt
2009Georgia Tech20RB
2010Georgia Tech20RB
2011Georgia Tech20RB
2012Georgia Tech20RB
2013Georgia Tech20RB6′0″

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/playPctileMedianTotalUsageAdj. rush
2013Georgia Tech1480.1577th (n=226)0.0722.417%0.08

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). Adjusted pass and rush: EPA per play adjusted for the defenses faced (CollegeFootballData’s WEPA). From CollegeFootballData, 2013 on.

Game by game

2013 Georgia Tech 13 games, 884 rushing yards, 11 TD
DateOpponentResultCarYdsTDLongRecRec yds
Aug 31vs.ElonW 70–⁠0747116159
Sep 14atDukeW 38–⁠141465011––
Sep 21vs.North CarolinaW 28–⁠201799219––
Sep 26vs.Virginia TechL 10–⁠17123719––
Oct 5atMiamiL 30–⁠451677219––
Oct 12atBYUL 20–⁠3862809––
Oct 19vs.SyracuseW 56–⁠01256011––
Oct 26atVirginiaW 35–⁠2512107236––
Nov 2vs.PittsburghW 21–⁠101894122––
Nov 14atClemsonL 31–⁠5582518––
Nov 23vs.Alabama A&MW 66–⁠78111139112
Nov 30vs.GeorgiaL 34–⁠4121100011––
Dec 30 ✦vs.Ole MissL 17–⁠25103807––
2012 Georgia Tech 12 games, 612 rushing yards, 4 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 3atVirginia TechL 17–⁠2013420815
Sep 22vs.MiamiL 36–⁠421202––
Sep 29vs.Middle TennesseeL 28–⁠4941907––
Oct 6atClemsonL 31–⁠47103608––
Oct 20vs.Boston CollegeW 37–⁠17135519––
Oct 27vs.BYUL 17–⁠411132011––
Nov 3atMarylandW 33–⁠1383306––
Nov 10atNorth CarolinaW 68–⁠501462111––
Nov 17vs.DukeW 42–⁠241170119––
Nov 24atGeorgiaL 10–⁠421471114––
Dec 1vs.Florida StateL 15–⁠211991013––
Dec 31 ✦vs.USCW 21–⁠7179901613
2011 Georgia Tech 12 games, 698 rushing yards, 7 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 1vs.Western CarolinaW 63–⁠2194419––
Sep 10atMiddle TennesseeW 49–⁠211291018––
Sep 17vs.KansasW 66–⁠24970221––
Sep 24vs.North CarolinaW 35–⁠281371022––
Oct 1atNC StateW 45–⁠3597304119
Oct 8vs.MarylandW 21–⁠161483039––
Oct 15atVirginiaL 21–⁠24113508––
Oct 22atMiamiL 7–⁠24102907112
Oct 29vs.ClemsonW 31–⁠171568111––
Nov 10vs.Virginia TechL 26–⁠37832011––
Nov 19atDukeW 38–⁠311366218––
Nov 26vs.GeorgiaL 17–⁠3112361818
2010 Georgia Tech 2 games, 58 rushing yards, 1 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 4vs.South Carolina StateW 41–⁠10334016––
Oct 16vs.Middle TennesseeW 42–⁠14424120––

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.