Defensive line, Fresno State, 2015–16
Nick Kristofors
- Number
- No. 99
- Height
- 6′3″
- Hometown
- Marin, CA
Nick Kristofors played defensive line at Fresno State (2015–16).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2016 | Fresno State | 27 | 19 | 1 | 1 | 1 | 1 |
Season lines from CollegeFootballData, regular season and bowls.
Defense before 2016
| Season | G | Solo | Ast | Tkl |
|---|---|---|---|---|
| 2015 | 9 of 12 | 2 | 1 | 3 |
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 |
|---|---|---|---|---|
| 2015 | Fresno State | 99 | DL | |
| 2016 | Fresno State | 99 | DL | 6′3″ |
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 Fresno State 10 games, 27 tackles, 1 sack
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 3 | at Nebraska | L 10–43 | 2 | 0 | 0 | 0 | 0 |
| Sep 17 | at Toledo | L 17–52 | 5 | 4 | 0 | 0 | 0 |
| Sep 24 | vs. Tulsa | L 41–48 | 2 | 2 | 0 | 0 | 0 |
| Oct 1 | at UNLV | L 20–45 | 3 | 2 | 0 | 0 | 0 |
| Oct 8 | at Nevada | L 22–27 | 6 | 6 | 1 | 1 | 0 |
| Oct 14 | vs. San Diego State | L 3–17 | 4 | 1 | 0 | 0 | 0 |
| Oct 22 | at Utah State | L 20–38 | 1 | 1 | 0 | 0 | 1 |
| Oct 28 | vs. Air Force | L 21–31 | 2 | 2 | 0 | 0 | 0 |
| Nov 5 | at Colorado State | L 0–37 | 1 | 0 | 0 | 0 | 0 |
| Nov 19 | vs. Hawai’i | L 13–14 | 1 | 1 | 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.