Running back, Georgia Tech, 2010–14
Charles Perkins
- Number
- No. 21
- Height
- 6′0″
- Hometown
- Lawrenceville, GA
Charles Perkins played running back at Georgia Tech (2010–14).
Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2011 | Georgia Tech | 28 | 95 | 3.4 | 1 | 14 |
| 2012 | Georgia Tech | 7 | 23 | 3.3 | 0 | 6 |
| 2013 | Georgia Tech | 13 | 114 | 8.8 | 2 | 31 |
| 2014 | Georgia Tech | 49 | 443 | 9.0 | 0 | 63 |
| Career | 97 | 675 | 7.0 | 3 | 63 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Ht |
|---|---|---|---|---|
| 2010 | Georgia Tech | 21 | RB | |
| 2011 | Georgia Tech | 21 | RB | |
| 2012 | Georgia Tech | 21 | RB | |
| 2013 | Georgia Tech | 21 | RB | |
| 2014 | Georgia Tech | 21 | RB | 6′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
| Season | Team | Plays | EPA/play | Pctile | Median | Total | Usage |
|---|---|---|---|---|---|---|---|
| 2013 | Georgia Tech | 10 | 0.20 | – | – | 2.0 | – |
| 2014 | Georgia Tech | 56 | 0.48 | – | – | 26.9 | 7% |
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, 443 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Aug 30 | vs. | W 38–19 | 3 | 19 | 0 | 17 | – | – |
| Sep 6 | at | W 38–21 | 4 | 33 | 0 | 11 | 1 | 4 |
| Sep 13 | vs. | W 42–38 | 2 | 59 | 0 | 63 | 1 | 1 |
| Oct 4 | vs. | W 28–17 | 7 | 65 | 0 | 25 | – | – |
| Oct 11 | vs. | L 25–31 | 1 | 6 | 0 | 6 | – | – |
| Oct 18 | at | L 43–48 | 7 | 79 | 0 | 15 | – | – |
| Oct 25 | at | W 56–28 | – | – | – | – | 1 | 79 |
| Nov 15 | vs. | W 28–6 | 3 | 11 | 0 | 4 | – | – |
| Nov 29 | at | W 30–24 | 6 | 48 | 0 | 25 | – | – |
| Dec 6 | vs. | L 35–37 | 9 | 64 | 0 | 20 | – | – |
| Dec 31 ✦ | vs. | W 49–34 | 7 | 59 | 0 | 23 | – | – |
2013 Georgia Tech 7 games, 114 rushing yards, 2 TD
2012 Georgia Tech 2 games, 23 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 3 | at | L 17–20 | 3 | 5 | 0 | 2 | – | – |
| Sep 8 | vs. | W 59–3 | 4 | 18 | 0 | 6 | – | – |
2011 Georgia Tech 8 games, 95 rushing yards, 1 TD
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 1 | vs. | W 63–21 | 5 | 12 | 0 | 4 | 1 | 9 |
| Sep 10 | at | W 49–21 | 5 | 22 | 0 | 14 | – | – |
| Sep 17 | vs. | W 66–24 | 4 | 15 | 1 | 5 | – | – |
| Sep 24 | vs. | W 35–28 | 1 | 2 | 0 | 2 | – | – |
| Oct 1 | at | W 45–35 | – | – | – | – | – | – |
| Oct 15 | at | L 21–24 | – | – | – | – | – | – |
| Nov 19 | at | W 38–31 | 12 | 45 | 0 | 9 | 1 | 29 |
| Dec 31 ✦ | vs. | L 27–30 | 1 | −1 | 0 | 0 | – | – |
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.
