Punter, Kent State, 2025–26
Jake Stoeckel
- Number
- No. 97
- Height
- 6′1″
- Weight
- 190 lb
- Class (2026)
- Freshman
- Hometown
- Sydney, NSW
Jake Stoeckel plays punter for Kent State.
2026 so far
30 punts, 42.8 average
Last game: at South Florida, L 2–29
Next game: vs. Akron, Oct 24
Filled bars: wins; outlined: losses.
Punting
* The season in progress, so far.
| Season | Team | Punts | Yds | Avg | Long | In 20 |
|---|---|---|---|---|---|---|
| 2025 | Kent State | 9 | 282 | 31.3 | 47 | 3 |
| 2026 | Kent State | 30 | 1,285 | 42.8 | 59 | 11 |
| Career | 39 | 1,567 | 40.2 | 59 | 14 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2025 | Kent State | 97 | P | Yr 1 | ||
| 2026 | Kent State | 97 | P | Fr. (Yr 2) | 6′1″ | 190 |
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 Kent State 7 games, 30 punts, 42.8 average
| Date | Opponent | Result | Punts | Yds | Long | In 20 |
|---|---|---|---|---|---|---|
| Sep 5 | at South Carolina | L 0–57 | 8 | 370 | 57 | 5 |
| Sep 12 | vs. Wofford | W 36–15 | 2 | 75 | 38 | 1 |
| Sep 19 | at Ohio State | L 3–59 | 5 | 214 | 49 | 0 |
| Sep 26 | vs. Ball State | W 26–13 | 5 | 191 | 46 | 4 |
| Oct 3 | vs. Ohio | L 10–13 | 2 | 87 | 47 | 1 |
| Oct 10 | at Western Michigan | L 7–38 | 4 | 185 | 59 | 0 |
| Oct 17 | at South Florida | L 2–29 | 4 | 163 | 45 | 0 |
2025 Kent State 3 games, 9 punts, 31.3 average
| Date | Opponent | Result | Punts | Yds | Long | In 20 |
|---|---|---|---|---|---|---|
| Aug 30 | vs. Merrimack | W 21–17 | 6 | 173 | 42 | 2 |
| Sep 6 | at Texas Tech | L 14–62 | 2 | 68 | 47 | 0 |
| Oct 4 | at Oklahoma | L 0–44 | 1 | 41 | 41 | 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.