Defensive back, Toledo, 2013–17
Kennedy Frazier
- Number
- No. 26
- Height
- 6′0″
- Weight
- 191 lb
- Hometown
- Baltimore, MD
Kennedy Frazier played defensive back at Toledo (2013–17).
Team titles: MAC champions, 2017
Defense
Season lines from CollegeFootballData, regular season and bowls.
Defense before 2016
| Season | G | Solo | Ast | Tkl |
|---|---|---|---|---|
| 2014 | 7 of 13 | 1 | 0 | 1 |
| 2015 | 6 of 12 | 4 | 1 | 5 |
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 Toledo 7 games, 9 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Aug 31 | vs. Elon | W 47–13 | 1 | 0 | 0 | 0 | 0 |
| Sep 16 | vs. Tulsa | W 54–51 | 2 | 2 | 0 | 0 | 0 |
| Oct 21 | vs. Akron | W 48–21 | 2 | 1 | 0 | 0 | 0 |
| Oct 26 | at Ball State | W 58–17 | 1 | 1 | 0 | 0 | 0 |
| Nov 2 | vs. Northern Illinois | W 27–17 | 1 | 1 | 0 | 0 | 0 |
| Nov 15 | at Bowling Green | W 66–37 | 1 | 1 | 0 | 0 | 0 |
| Dec 2 | vs.Akron | W 45–28 | 1 | 0 | 0 | 0 | 0 |
2016 Toledo 1 game, 1 tackle
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 10 | vs. Maine | W 45–3 | 1 | 1 | 0 | 0 | 0 |
2015 Toledo 1 game, 1 return, 0 yards
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 26 | vs. Arkansas State | W 37–7 | – | – | – | – | – |
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.