Linebacker, Virginia Tech, 2019–22
J.R. Walker
- Number
- No. 19
- Height
- 6′0″
- Weight
- 223 lb
- Class (2022)
- Junior
- Hometown
- Clayton, NC
J.R. Walker played linebacker at Virginia Tech (2019–22).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2020 | Virginia Tech | 6 | 2 | 0 | 0 | 0 | 0 |
| 2022 | Virginia Tech | 18 | 8 | 2 | 0 | 0 | 2 |
| Career | 24 | 10 | 2 | 0 | 0 | 2 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2019 | Virginia Tech | 19 | LB | RS | ||
| 2020 | Virginia Tech | 19 | LB | Fr. | ||
| 2021 | Virginia Tech | 19 | LB | So. | ||
| 2022 | Virginia Tech | 19 | LB | Jr. | 6′0″ | 223 |
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
2022 Virginia Tech 8 games, 18 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 10 | vs. Boston College | W 27–10 | 3 | 2 | 0 | 0 | 0 |
| Sep 17 | vs. Wofford | W 27–7 | 3 | 0 | 0.5 | 0 | 0 |
| Oct 8 | at Pittsburgh | L 29–45 | 4 | 1 | 0 | 0 | 0 |
| Oct 15 | vs. Miami | L 14–20 | 4 | 2 | 1.5 | 0 | 0 |
| Oct 27 | at NC State | L 21–22 | 2 | 1 | 0 | 0 | 0 |
| Nov 5 | vs. Georgia Tech | L 27–28 | 0 | 0 | 0 | 0 | 0 |
| Nov 12 | at Duke | L 7–24 | 1 | 1 | 0 | 0 | 0 |
| Nov 19 | at Liberty | W 23–22 | 1 | 1 | 0 | 0 | 0 |
2020 Virginia Tech 3 games, 6 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 26 | vs.NC State | W 45–24 | 1 | 1 | 0 | 0 | 0 |
| Oct 10 | at North Carolina | L 45–56 | 3 | 1 | 0 | 0 | 0 |
| Dec 12 | vs. Virginia | W 33–15 | 2 | 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.