Defensive end, Troy, 2016
Junior Gnonkonde
- Number
- No. 44
- Height
- 6′4″
- Hometown
- Lakeland, GA
Junior Gnonkonde played defensive end at Troy (2016).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2016 | Troy | 36 | 27 | 3 | 2 | 7 | 2 |
Season lines from CollegeFootballData, regular season and bowls.
Defense before 2016
| Season | G | Solo | Ast | Tkl |
|---|---|---|---|---|
| 2014 | 7 of 13 | 7 | 17 | 24 |
Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources: ESPN play-by-play participants, via SportsDataverse: tackles only, counted in the games whose play-by-play names tacklers (G: those games, of his team’s), so part of the season, not its total. A dash: the source has no number for it.
On the roster
| Season | Team | No. | Pos | Ht |
|---|---|---|---|---|
| 2016 | Troy | 44 | DE | 6′4″ |
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 Troy 11 games, 36 tackles, 2 sacks
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 3 | vs. Austin Peay | W 57–17 | 6 | 6 | 0 | 0 | 0 |
| Sep 10 | at Clemson | L 24–30 | 3 | 2 | 0 | 0 | 3 |
| Sep 24 | vs. New Mexico State | W 52–6 | 1 | 0 | 0 | 0 | 0 |
| Oct 1 | at Idaho | W 34–13 | 3 | 3 | 0 | 0 | 0 |
| Oct 15 | vs. Georgia State | W 31–21 | 2 | 2 | 1 | 1 | 1 |
| Oct 20 | at South Alabama | W 28–21 | 5 | 5 | 1 | 1 | 1 |
| Nov 5 | vs. Massachusetts | W 52–31 | 1 | 1 | 0 | 0 | 0 |
| Nov 12 | vs. App State | W 28–24 | 4 | 3 | 0 | 0 | 0 |
| Nov 17 | vs. Arkansas State | L 3–35 | 3 | 3 | 0 | 0 | 1 |
| Nov 26 | at Texas State | W 40–7 | 2 | 2 | 1 | 0 | 1 |
| Dec 3 | at Georgia Southern | L 24–28 | 6 | 0 | 0 | 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.