Safety, Akron, 2013–⁠17

Zach Guiser

Number
No. 32
Height
6′1″
Weight
195 lb
Hometown
Fayette City, PA

Zach Guiser played safety at Akron (2013–⁠17).

Career highs

15tackles, career highvs. App State, 2016

Defense

Tackles, season by season, with his team’s record
SeasonTeamTklSoloTFLSacksIntPDHur
2015Akron––––1––
2016Akron532621121
2017Akron161410110
Career694031331

Season lines from CollegeFootballData, regular season and bowls. A dash: the source has no number for that season (often an FCS season), and career totals count only the numbers on file.

Defense before 2016

SeasonGSoloAstTkl
20148 of 12303
201512 of 13331548

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

SeasonTeamNo.PosHtWt
2013Akron32S
2014Akron32S
2015Akron32S
2016Akron32S
2017Akron32S6′1″195

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 Akron 2 games, 16 tackles, 1 INT
DateOpponentResultTklSoloTFLSacksIntPD
Sep 2atPenn StateL 0–⁠521081010
Sep 16vs.Iowa StateL 14–⁠41660001
2016 Akron 8 games, 53 tackles, 1 sack, 1 INT
DateOpponentResultTklSoloTFLSacksIntPD
Sep 3vs.VMIW 47–⁠24221001
Sep 10atWisconsinL 10–⁠54850000
Sep 17atMarshallW 65–⁠38720010
Sep 24vs.App StateL 38–⁠451570000
Oct 1atKent StateW 31–⁠27641100
Oct 8vs.Miami (OH)W 35–⁠13630000
Oct 15vs.Western MichiganL 0–⁠41710001
Nov 22atOhioL 3–⁠9220000
2015 Akron 1 game, 1 INT
DateOpponentResultTklSoloTFLSacksIntPD
Oct 10atEastern MichiganW 47–⁠21––––1–

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.