Defensive line, Elon, 2016–17
Nick Groll
- Number
- No. 94
- Height
- 6′6″
- Weight
- 279 lb
- Hometown
- Andrews, TX
Nick Groll played defensive line at Elon (2016–17).
Defense
Season lines from CollegeFootballData, regular season and bowls.
Defense before 2016
| Season | G | Solo | Tkl |
|---|---|---|---|
| 2015 | 1 of 1 | 1 | 1 |
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
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 Elon 1 game, 3 tackles, 1 sack
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Aug 31 | at Toledo | L 13–47 | 3 | 2 | 1 | 1 | 0 |
No box score in the source for Sep 9 at Furman; Sep 16 vs. Charleston Southern; Sep 23 at Richmond; Sep 30 vs. UAlbany; Oct 7 vs. William & Mary; Oct 21 at Rhode Island; Oct 28 at Villanova; Nov 4 vs. Towson; Nov 11 at New Hampshire; Nov 18 vs. James Madison; Nov 25 vs. Furman, so those games are not listed.
2016 Elon 1 game, 2 tackles, 1 sack
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 10 | at Charlotte | L 14–47 | 2 | 1 | 1 | 1 | 0 |
No box score in the source for Sep 3 vs. Gardner-Webb; Sep 17 vs. Fayetteville State; Sep 24 at William & Mary; Oct 1 vs. Villanova; Oct 7 vs. New Hampshire; Oct 22 vs. Richmond; Oct 29 at UAlbany; Nov 5 at Towson; Nov 12 vs. Rhode Island; Nov 19 at James Madison, 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.