Linebacker, Northwestern State, 2016–17
Chrishard Buhl
- Number
- No. 38
- Height
- 6′2″
- Weight
- 214 lb
- Hometown
- Chicago, IL
Chrishard Buhl played linebacker at Northwestern State (2016–17).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2016 | Northwestern State | 2 | 2 | 0 | 0 | 0 | 0 |
| 2017 | Northwestern State | 3 | 3 | 0 | 0 | 0 | 0 |
| Career | 5 | 5 | 0 | 0 | 0 | 0 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Ht | Wt |
|---|---|---|---|---|---|
| 2016 | Northwestern State | 38 | LB | ||
| 2017 | Northwestern State | 38 | LB | 6′2″ | 214 |
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
2017 Northwestern State 1 game, 3 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 2 | at Louisiana Tech | L 24–52 | 3 | 3 | 0 | 0 | 0 |
No box score in the source for Sep 9 at Grambling; Sep 16 vs. Lamar; Sep 30 vs. SE Louisiana; Oct 7 at Nicholls; Oct 14 at Sam Houston; Oct 21 vs. Central Arkansas; Oct 28 at Houston Christian; Nov 4 vs. Abilene Christian; Nov 12 at McNeese; Nov 18 vs. Stephen F. Austin, so those games are not listed.
2016 Northwestern State 1 game, 2 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 2 | at Baylor | L 7–55 | 2 | 2 | 0 | 0 | 0 |
No box score in the source for Sep 8 vs. Incarnate Word; Sep 17 at Central Arkansas; Sep 24 at SE Louisiana; Oct 8 vs. Kentucky Wesleyan; Oct 15 at Lamar; Oct 22 vs. McNeese; Oct 29 vs. Nicholls; Nov 5 at Abilene Christian; Nov 13 vs. Sam Houston; Nov 19 at Stephen F. Austin, so those games are not listed.
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.