Defensive end, Georgia Tech, 2015–16
Rod Rook-Chungong
- Number
- No. 41
- Height
- 6′3″
- Hometown
- Silver Spring, MD
Rod Rook-Chungong played defensive end at Georgia Tech (2015–16).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | Int | PD | Hur |
|---|---|---|---|---|---|---|---|---|
| 2015 | Georgia Tech | – | – | – | – | 1 | – | – |
| 2016 | Georgia Tech | 32 | 20 | 4.5 | 0 | 0 | 0 | 0 |
| Career | 32 | 20 | 4.5 | 0 | 1 | 0 | 0 | |
Season lines from CollegeFootballData, regular season and bowls. A dash: the source has no number for that season (often an FCS season), and career totals count only the numbers on file.
On the roster
| Season | Team | No. | Pos | Ht |
|---|---|---|---|---|
| 2015 | Georgia Tech | 41 | DE | |
| 2016 | Georgia Tech | 41 | DE | 6′3″ |
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
2016 Georgia Tech 11 games, 32 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 3 | vs. | W 17–14 | 6 | 4 | 0 | 0 | 0 | 0 |
| Sep 10 | vs. | W 35–10 | 3 | 3 | 0 | 0 | 0 | 0 |
| Sep 22 | vs. | L 7–26 | 4 | 2 | 0 | 0 | 0 | 0 |
| Oct 1 | vs. | L 21–35 | 1 | 0 | 0.5 | 0 | 0 | 0 |
| Oct 8 | at | L 34–37 | 2 | 0 | 0 | 0 | 0 | 0 |
| Oct 15 | vs. | W 35–24 | 3 | 3 | 3 | 0 | 0 | 0 |
| Oct 29 | vs. | W 38–35 | 1 | 1 | 0 | 0 | 0 | 0 |
| Nov 12 | at | W 30–20 | 4 | 4 | 1 | 0 | 0 | 0 |
| Nov 19 | vs. | W 31–17 | 2 | 2 | 0 | 0 | 0 | 0 |
| Nov 26 | at | W 28–27 | 3 | 0 | 0 | 0 | 0 | 0 |
| Dec 31 ✦ | vs. | W 33–18 | 3 | 1 | 0 | 0 | 0 | 0 |
2015 Georgia Tech 1 game, 1 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Oct 31 | at | L 21–27 | – | – | – | – | 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.
