Linebacker, Georgia State, 2019–21
Zach Dixon
- Number
- No. 32
- Height
- 6′1″
- Weight
- 215 lb
- Class (2021)
- Junior
- Hometown
- Miami, FL
Zach Dixon played linebacker at Georgia State (2019–21).
Career highs
9tackles, career highvs. Army, 2019Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2019 | Georgia State | 37 | 24 | 1 | 1 | 1 | 0 |
| 2021 | Georgia State | 9 | 6 | 0 | 0 | 0 | 0 |
| Career | 46 | 30 | 1 | 1 | 1 | 0 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2019 | Georgia State | 32 | LB | Fr. | ||
| 2020 | Georgia State | 32 | LB | So. | ||
| 2021 | Georgia State | 32 | LB | Jr. | 6′1″ | 215 |
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
2021 Georgia State 4 games, 9 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Oct 2 | vs. App State | L 16–45 | 1 | 1 | 0 | 0 | 0 |
| Oct 9 | at UL Monroe | W 55–21 | 1 | 0 | 0 | 0 | 0 |
| Nov 27 | vs. Troy | W 37–10 | 4 | 3 | 0 | 0 | 0 |
| Dec 25 ✦ | vs. Ball State | W 51–20 | 3 | 2 | 0 | 0 | 0 |
2019 Georgia State 7 games, 37 tackles, 1 sack
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Oct 19 | vs. Army | W 28–21 | 9 | 5 | 0 | 0 | 0 |
| Oct 26 | vs.Troy | W 52–33 | 3 | 1 | 0 | 0 | 0 |
| Nov 9 | atUL Monroe | L 31–45 | 8 | 3 | 0 | 0 | 0 |
| Nov 16 | vs.App State | L 27–56 | 8 | 8 | 0 | 0 | 0 |
| Nov 23 | vs. South Alabama | W 28–15 | 4 | 4 | 1 | 1 | 0 |
| Nov 30 | at Georgia Southern | L 10–38 | 4 | 2 | 0 | 0 | 0 |
| Dec 31 ✦ | vs. Wyoming | L 17–38 | 1 | 1 | 0 | 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.