Kicker, Sacred Heart, 2025–26
Ryan Bocklet
- Number
- No. 39
- Height
- 6′1″
- Weight
- 215 lb
- Class (2026)
- Sophomore
- Hometown
- Souderton, PA
Ryan Bocklet plays kicker for Sacred Heart.
2026 so far
5 of 6 field goals
Last game: vs. Hampton, W 35–21
Next game: at Stony Brook, Oct 31
Filled bars: wins; outlined: losses.
Kicking
| Season | Team | FGM | FGA | Pct | Long | XP | Pts |
|---|---|---|---|---|---|---|---|
| 2025 | Sacred Heart | 0 | 0 | – | 0 | 4 | 4 |
| 2026 | Sacred Heart | 5 | 6 | 83.3 | 40 | 18 | 33 |
| Career | 5 | 6 | 83.3 | 40 | 22 | 37 | |
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
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2025 | Sacred Heart | 39 | PK | Fr. | ||
| 2026 | Sacred Heart | 39 | PK | So. | 6′1″ | 215 |
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 Sacred Heart 7 games, 5 of 6 field goals
| Date | Opponent | Result | FGM | FGA | Long | XP | Pts |
|---|---|---|---|---|---|---|---|
| Sep 5 | at Monmouth | L 24–31 | 1 | 2 | 23 | 3 | 6 |
| Sep 12 | at Massachusetts | L 10–37 | 1 | 1 | 35 | 1 | 4 |
| Sep 19 | at Elon | L 21–24 | 0 | 0 | 0 | 3 | 3 |
| Sep 26 | vs. New Hampshire | W 20–13 | 2 | 2 | 30 | 2 | 8 |
| Oct 3 | at Maine | W 24–16 | 1 | 1 | 40 | 3 | 6 |
| Oct 10 | vs. Stonehill | L 7–28 | 0 | 0 | 0 | 1 | 1 |
| Oct 17 | vs. Hampton | W 35–21 | 0 | 0 | 0 | 5 | 5 |
2025 Sacred Heart 1 game, 4 of 4 extra points
| Date | Opponent | Result | FGM | FGA | Long | XP | Pts |
|---|---|---|---|---|---|---|---|
| Nov 8 | vs.Virginia Lynchburg | W 56–10 | 0 | 0 | 0 | 4 | 4 |
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.