Linebacker, North Carolina, 2019–23
Jake Harkleroad
- Number
- No. 45
- Height
- 5′10″
- Weight
- 215 lb
- Class (2023)
- Senior
- Hometown
- Charlotte, NC
Jake Harkleroad played linebacker at North Carolina (2019–23).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2020 | North Carolina | 2 | 2 | 0 | 0 | 0 | 0 |
| 2022 | North Carolina | 9 | 4 | 0 | 0 | 0 | 0 |
| 2023 | North Carolina | 3 | 1 | 0 | 0 | 0 | 0 |
| Career | 14 | 7 | 0 | 0 | 0 | 0 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2019 | North Carolina | 45 | LB | RS | ||
| 2020 | North Carolina | 45 | LB | Fr. | ||
| 2021 | North Carolina | 45 | LB | So. | ||
| 2022 | North Carolina | 45 | LB | Jr. | ||
| 2023 | North Carolina | 45 | LB | Sr. | 5′10″ | 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
2023 North Carolina 2 games, 3 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 23 | at | W 41–24 | 2 | 1 | 0 | 0 | 0 |
| Oct 14 | vs. | W 41–31 | 1 | 0 | 0 | 0 | 0 |
2022 North Carolina 5 games, 9 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Oct 1 | vs. | W 41–10 | 3 | 2 | 0 | 0 | 0 |
| Oct 8 | at | W 27–24 | 3 | 1 | 0 | 0 | 0 |
| Nov 5 | at | W 31–28 | 1 | 0 | 0 | 0 | 0 |
| Nov 12 | at | W 36–34 | 1 | 0 | 0 | 0 | 0 |
| Nov 25 | vs. | L 27–30 | 1 | 1 | 0 | 0 | 0 |
2020 North Carolina 1 game, 2 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Dec 5 | vs. | W 49–9 | 2 | 2 | 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.
