
Tight end, Boston College, 2015–19
Jake Burt
- Number
- No. 84
- Height
- 6′3″
- Weight
- 260 lb
- Class (2019)
- Senior
- Hometown
- Lynnfield, MA
- Born
- Aug 25, 1996
Wikipedia readers: about 127 a month over the past year
Jake Burt played tight end at Boston College (2015–19).
Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2015 | Boston College | 1 | 7 | 7.0 | 0 | 7 |
| 2017 | Boston College | 1 | 5 | 5.0 | 0 | 5 |
| 2018 | Boston College | 6 | 83 | 13.8 | 1 | 25 |
| 2019 | Boston College | 15 | 212 | 14.1 | 1 | 55 |
| Career | 23 | 307 | 13.3 | 2 | 55 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2015 | Boston College | 84 | TE | Yr 1 | ||
| 2016 | Boston College | 84 | TE | Yr 2 | ||
| 2017 | Boston College | 84 | TE | Yr 3 | ||
| 2018 | Boston College | 84 | TE | Yr 4 | ||
| 2019 | Boston College | 84 | TE | Sr. (Yr 5) | 6′3″ | 260 |
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 |
|---|---|---|---|---|---|---|---|
| 2015 | Boston College | 1 | 0.50 | – | – | 0.5 | – |
| 2017 | Boston College | 1 | 0.10 | – | – | 0.1 | – |
| 2018 | Boston College | 6 | 1.61 | – | – | 9.7 | – |
| 2019 | Boston College | 17 | 1.17 | – | – | 19.9 | – |
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
2019 Boston College 7 games, 15 catches, 212 yards, 1 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Aug 31 | vs. | W 35–28 | 1 | 3 | 0 | 3 |
| Sep 7 | vs. | W 45–13 | 1 | 55 | 1 | 55 |
| Sep 13 | vs. | L 24–48 | 3 | 16 | 0 | 8 |
| Sep 21 | at | W 30–16 | 2 | 24 | 0 | 17 |
| Sep 28 | vs. | L 24–27 | 2 | 20 | 0 | 11 |
| Oct 5 | at | L 39–41 | 2 | 28 | 0 | 31 |
| Nov 9 | vs. | L 31–38 | 4 | 66 | 0 | 23 |
2018 Boston College 5 games, 6 catches, 83 yards, 1 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 1 | vs. | W 55–21 | 2 | 31 | 0 | 25 |
| Sep 22 | at | L 13–30 | 1 | 24 | 0 | 24 |
| Oct 26 | vs. | W 27–14 | 1 | 23 | 0 | 23 |
| Nov 3 | at | W 31–21 | 1 | 2 | 0 | 2 |
| Nov 24 | vs. | L 21–42 | 1 | 3 | 1 | 3 |
2017 Boston College 1 game, 1 catch, 5 yards
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 16 | vs. | L 20–49 | 1 | 5 | 0 | 5 |
2015 Boston College 1 game, 1 catch, 7 yards
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 12 | vs. | W 76–0 | 1 | 7 | 0 | 7 |
Box scores from CollegeFootballData, 2004 on. ✦ postseason; ★ a career high on file.
Other pro football
| Years | League | Team |
|---|---|---|
| 2021–22 | CFL | Hamilton Tiger-Cats |
Leagues other than the NFL, from the infobox of his Wikipedia article (CC BY-SA), as it names the teams.
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.