Cornerback, Stephen F. Austin, 2016–17
Zack Kanipes
- Number
- No. 40
- Height
- 5′7″
- Weight
- 165 lb
- Hometown
- Llano, TX
Zack Kanipes played cornerback at Stephen F. Austin (2016–17).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2016 | Stephen F. Austin | 4 | 2 | 1 | 1 | 0 | 0 |
| 2017 | Stephen F. Austin | 1 | 1 | 0 | 0 | 0 | 0 |
| Career | 5 | 3 | 1 | 1 | 0 | 0 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Ht | Wt |
|---|---|---|---|---|---|
| 2016 | Stephen F. Austin | 40 | CB | ||
| 2017 | Stephen F. Austin | 40 | CB | 5′7″ | 165 |
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 Stephen F. Austin 1 game, 1 tackle
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 2 | at SMU | L 14–58 | 1 | 1 | 0 | 0 | 0 |
No box score in the source for Sep 9 vs. Southern Utah; Sep 16 vs. Incarnate Word; Sep 23 at Abilene Christian; Sep 30 vs. McNeese; Oct 7 vs. Sam Houston; Oct 14 at Central Arkansas; Oct 21 vs. Houston Christian; Oct 28 at Lamar; Nov 11 vs. Nicholls; Nov 18 at Northwestern State, so those games are not listed.
2016 Stephen F. Austin 1 game, 4 tackles, 1 sack
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 3 | at Texas Tech | L 17–69 | 4 | 2 | 1 | 1 | 0 |
No box score in the source for Sep 10 vs. West Alabama; Sep 17 at McNeese; Sep 24 vs. Abilene Christian; Oct 1 at Sam Houston; Oct 8 at Nicholls; Oct 15 vs. SE Louisiana; Oct 29 at Incarnate Word; Nov 5 vs. Central Arkansas; Nov 12 at Houston Christian; Nov 19 vs. Northwestern State, 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.