Tight end, Toledo (from Holy Cross), 2022–25
Jacob Petersen
- Number
- No. 89
- Height
- 6′4″
- Weight
- 250 lb
- Class (2025)
- Senior
- Hometown
- Spring Grove, IL
Jacob Petersen played tight end at Holy Cross (2022–24) and Toledo (2025).
Career highs
6catches, career highvs. New Hampshire, 2024110receiving yards, career highvs. New Hampshire, 20242receiving touchdowns, career highvs. Fordham, 2024Team titles: Patriot League champions, 2022, 2023 and 2024
Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2023 | Holy Cross | 5 | 86 | 17.2 | 1 | 29 |
| 2024 | Holy Cross | 33 | 482 | 14.6 | 6 | 75 |
| 2025 | Toledo | 25 | 335 | 13.4 | 3 | 28 |
| Career | 63 | 903 | 14.3 | 10 | 75 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2022 | Holy Cross | 89 | TE | Fr. | ||
| 2023 | Holy Cross | 89 | TE | So. | ||
| 2024 | Holy Cross | 89 | TE | Jr. | ||
| 2025 | Toledo | 89 | TE | Sr. | 6′4″ | 250 |
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.
Per play
| Season | Team | Plays | EPA/play | Pctile | Median | Total | Usage |
|---|---|---|---|---|---|---|---|
| 2023 | Holy Cross (FCS) | 5 | 0.76 | – | – | 3.8 | – |
| 2024 | Holy Cross (FCS) | 43 | 0.87 | 42nd (n=581) | 0.92 | 37.5 | 7% |
| 2025 | Toledo | 37 | 0.50 | 58th (n=1040) | 0.46 | 18.7 | 4% |
Expected points added: how much the player’s plays moved the team’s expected score, per play and in total. Plays: total EPA divided by EPA per play, the plays the source credits to him (for a receiver roughly his catches and runs, not every target; for a passer, not every attempt), so it can differ from attempts plus carries. Percentile: against the position’s regulars that season across all divisions on file (quarterbacks with 150+ plays, backs 60+, receivers and tight ends 30+), with how many there were (n) and their median; a dash means too few plays to rank. A season in progress uses the full-season bar scaled by games played, never below 75 plays for quarterbacks, 30 for backs and 20 for receivers. The cohort grows or shrinks with the source’s coverage each season (2025 lists far more players), so compare percentiles rather than raw EPA across years. FCS seasons are marked. Usage: the share of the team’s plays the player was part of (shown from 20 plays). From CollegeFootballData, 2013 on.
Game by game
2025 Toledo 13 games, 25 catches, 335 yards, 3 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Aug 30 | at | L 16–24 | 2 | 21 | 0 | 14 |
| Sep 6 | vs. | W 45–21 | 2 | 40 | 0 | 26 |
| Sep 13 | vs. | W 60–0 | 1 | 21 | 0 | 21 |
| Sep 20 | at | L 13–14 | 2 | 12 | 0 | 10 |
| Sep 27 | vs. | W 45–3 | 1 | 28 | 0 | 28 |
| Oct 11 | at | L 23–28 | 2 | 41 | 1 | 24 |
| Oct 18 | vs. | W 45–10 | 1 | 12 | 0 | 12 |
| Oct 25 | at | L 7–28 | 5 | 58 | 0 | 21 |
| Nov 5 | vs. | W 42–3 | 2 | 13 | 0 | 7 |
| Nov 12 | at | W 24–3 | 2 | 12 | 1 | 6 |
| Nov 22 | vs. | W 38–9 | 1 | 10 | 0 | 10 |
| Nov 29 | at | W 21–3 | 1 | 7 | 0 | 7 |
| Dec 23 ✦ | vs. | L 22–27 | 3 | 60 | 1 | 26 |
2024 Holy Cross 10 games, 33 catches, 482 yards, 6 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Aug 31 | at | L 17–20 | 4 | 43 | 0 | 17 |
| Sep 7 | vs. | L 20–21 | 6 | 110 | 1 | 71 |
| Sep 14 | at | W 43–22 | 3 | 46 | 0 | 22 |
| Sep 21 | vs. | L 31–38 | 1 | 32 | 0 | 32 |
| Sep 28 | at | L 14–42 | 4 | 48 | 1 | 27 |
| Oct 5 | at | W 38–7 | 2 | 21 | 0 | 21 |
| Oct 12 | vs. | W 19–16 | 2 | 9 | 2 | 6 |
| Oct 19 | at | L 34–35 | 4 | 53 | 1 | 25 |
| Nov 9 | vs. | L 7–10 | 4 | 30 | 1 | 10 |
| Nov 16 | vs. | W 40–38 | 3 | 90 | 0 | 75 |
2023 Holy Cross 4 games, 5 catches, 86 yards, 1 TD
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.
