Safety, Toledo, 2023–26
Dylan Hohler
- Number
- No. 39
- Height
- 6′4″
- Weight
- 196 lb
- Class (2026)
- Junior
- Hometown
- Huron, OH
Dylan Hohler plays safety for Toledo. Last time out, against Central Connecticut: 1 tackles.
2026 so far
2 tackles
Last game: 1 tackles vs. Central Connecticut, W 63–10
Next game: vs. Western Michigan, Oct 24
Filled bars: wins; outlined: losses.
Defense
* The season in progress, so far.
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.
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
2026 Toledo 2 games, 2 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 4 | at Michigan State | L 20–30 | 1 | 0 | 0 | 0 | 0 | 0 |
| Sep 12 | vs. Central Connecticut | W 63–10 | 1 | 1 | 0 | 0 | 0 | 0 |
2025 Toledo 6 games, 7 tackles, 1 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 6 | vs. Western Kentucky | W 45–21 | 2 | 1 | 0 | 0 | 0 | 0 |
| Sep 13 | vs. Morgan State | W 60–0 | 0 | 0 | 0 | 0 | 0 | 1 |
| Sep 27 | vs. Akron | W 45–3 | 1 | 1 | 0 | 0 | 0 | 0 |
| Oct 25 | at Washington State | L 7–28 | 1 | 1 | 0 | 0 | 0 | 0 |
| Nov 22 | vs. Ball State | W 38–9 | 1 | 1 | 1 | 0 | 1 | 0 |
| Dec 23 ✦ | vs. Louisville | L 22–27 | 2 | 0 | 0 | 0 | 0 | 0 |
2024 Toledo 2 games, 2 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Aug 29 | vs. Duquesne | W 49–10 | 1 | 0 | 0 | 0 | 0 | 0 |
| Nov 12 | vs. Central Michigan | W 37–10 | 1 | 0 | 0 | 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.