Quarterback, Georgia Tech, 2008–09
Jaybo Shaw
- Number
- No. 11
- Height
- 6′0″
- Hometown
- Flowery Branch, GA
Jaybo Shaw played quarterback at Georgia Tech (2008–09).
Career highs
230passing yards, career highvs. Duke, 2008Team titles: ACC champions, 2009
Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2008* | Georgia Tech | 63 | 200 | 3.2 | 3 | 43 |
| 2009 | Georgia Tech | 12 | 51 | 4.3 | 0 | 16 |
| Career | 75 | 251 | 3.3 | 3 | 43 | |
Season lines from CollegeFootballData, regular season and bowls. * That team-season’s player lines are missing part of the team’s yards in our source, so these numbers may be short.
On the roster
| Season | Team | No. | Pos | Ht |
|---|---|---|---|---|
| 2008 | Georgia Tech | 11 | QB | |
| 2009 | Georgia Tech | 11 | QB | 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.
Game by game
2009 Georgia Tech 4 games, 18 passing yards
| Date | Opponent | Result | Car | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Oct 24 | at Virginia | W 34–9 | 1 | 2 | 0 | 2 |
| Oct 31 | at Vanderbilt | W 56–31 | 4 | 22 | 0 | 11 |
| Nov 14 | at Duke | W 49–10 | 6 | 27 | 0 | 16 |
| Nov 28 | vs. Georgia | L 24–30 | 1 | 0 | 0 | 0 |
2008 Georgia Tech 7 games, 200 rushing yards, 3 TD
| Date | Opponent | Result | Car | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Aug 28 | vs. Jacksonville State | W 41–14 | 9 | 51 | 1 | 43 |
| Sep 20 | vs. Mississippi State | W 38–7 | 9 | 61 | 1 | 25 |
| Oct 4 | vs.Duke | W 27–0 | 18 | 13 | 1 | 7 |
| Nov 1 | vs. Florida State | W 31–28 | 7 | 5 | 0 | 5 |
| Nov 8 | at North Carolina | L 7–28 | 8 | 21 | 0 | 9 |
| Nov 20 | vs. Miami | W 41–23 | 10 | 47 | 0 | 27 |
| Nov 29 | atGeorgia | W 45–42 | 2 | 2 | 0 | 1 |
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.