Running back, Georgia Tech, 2008–11
Richard Watson
- Number
- No. 32
- Height
- 6′1″
- Hometown
- Tallahassee, FL
Richard Watson played running back at Georgia Tech (2008–11).
Team titles: ACC champions, 2009
Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2009 | Georgia Tech | 9 | 37 | 4.1 | 1 | 9 |
| 2010 | Georgia Tech | 10 | 32 | 3.2 | 0 | 7 |
| 2011 | Georgia Tech | 3 | 30 | 10.0 | 0 | 28 |
| On file (2009–11) | 22 | 99 | 4.5 | 1 | 28 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Ht |
|---|---|---|---|---|
| 2009 | Georgia Tech | 32 | RB | |
| 2010 | Georgia Tech | 32 | RB | |
| 2011 | Georgia Tech | 32 | RB | 6′1″ |
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
2011 Georgia Tech 2 games, 30 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 1 | vs. Western Carolina | W 63–21 | 3 | 30 | 0 | 28 |
| Nov 19 | at Duke | W 38–31 | – | – | – | – |
2010 Georgia Tech 4 games, 32 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 4 | vs. South Carolina State | W 41–10 | 3 | 10 | 0 | 4 |
| Oct 9 | vs. Virginia | W 33–21 | 2 | 5 | 0 | 3 |
| Oct 16 | vs. Middle Tennessee | W 42–14 | 3 | 13 | 0 | 7 |
| Nov 4 | at Virginia Tech | L 21–28 | 2 | 4 | 0 | 4 |
2009 Georgia Tech 4 games, 37 rushing yards, 1 TD
| Date | Opponent | Result | Car | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 5 | vs. Jacksonville State | W 37–17 | 4 | 25 | 0 | 9 |
| Oct 24 | atVirginia | W 34–9 | 2 | 2 | 0 | 1 |
| Oct 31 | at Vanderbilt | W 56–31 | 1 | 2 | 0 | 2 |
| Nov 14 | atDuke | W 49–10 | 2 | 8 | 1 | 7 |
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.