South Carolina, 2009–10
Jarvis Giles
Lettered 2009 (school media guide)
- Number
- No. 3
- Height
- 5′11″
- Hometown
- Tampa, FL
Jarvis Giles played at South Carolina (2009–10).
Career highs
113rushing yards, career highvs. Florida Atlantic, 2009Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2009 | South Carolina | 52 | 277 | 5.3 | 1 | 38 |
| 2010 | South Carolina | 2 | 12 | 6.0 | 0 | 8 |
| Career | 54 | 289 | 5.4 | 1 | 38 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Ht |
|---|---|---|---|---|
| 2009 | South Carolina | 3 | ||
| 2010 | South Carolina | 3 | 5′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.
Game by game
2010 South Carolina 1 game, 12 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 2 | vs. Southern Miss | W 41–13 | 2 | 12 | 0 | 8 | – | – |
2009 South Carolina 9 games, 277 rushing yards, 1 TD
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 3 | at NC State | W 7–3 | 5 | 13 | 0 | 22 | – | – |
| Sep 12 | at Georgia | L 37–41 | 10 | 23 | 0 | 6 | 3 | 19 |
| Sep 19 | vs. Florida Atlantic | W 38–16 | 11 | 113 | 1 | 38 | – | – |
| Sep 24 | vs. Ole Miss | W 16–10 | 2 | 8 | 0 | 8 | – | – |
| Oct 3 | vs. South Carolina State | W 38–14 | 11 | 74 | 0 | 33 | 1 | 5 |
| Oct 10 | vs. Kentucky | W 28–26 | 3 | 14 | 0 | 14 | 1 | 2 |
| Oct 24 | vs. Vanderbilt | W 14–10 | 3 | 11 | 0 | 5 | – | – |
| Oct 31 | at Tennessee | L 13–31 | 3 | 8 | 0 | 4 | – | – |
| Nov 7 | at Arkansas | L 16–33 | 4 | 13 | 0 | 9 | – | – |
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.