Tight end, Duke, 2022–⁠26

Jeremiah Hasley

Lettered 2023–⁠25 (school media guide)

Number
No. 85
Height
6′3″
Weight
250 lb
Class (2026)
Senior
Hometown
Gibsonia, PA

Jeremiah Hasley plays tight end for Duke. Last time out, against North Carolina: 2 catches, 16 yards.

2026 so far

21 catches, 250 yards

Last game: 2 catches, 16 yards vs. North Carolina, L 20–⁠24

Next game: at Virginia, Oct 23

Game by game this season, receiving yards
  1. 36TULN
  2. 53@ILL
  3. 88STAN
  4. 18W&M
  5. 39@GT
  6. 16UNC

Filled bars: wins; outlined: losses.

Career highs

7catches, career highat North Carolina, 202588receiving yards, career highvs. Stanford, 20262receiving touchdowns, career highvs. Virginia, 2025

Team titles: ACC champions, 2025

Receiving

Receiving yards, season by season, with his team’s record

* The season in progress, so far.

SeasonTeamRecYdsAvgTDLong
2023Duke55210.4121
2024Duke3113.717
2025Duke4045411.3656
2026Duke2125011.9035
Career6976711.1856

Defense

SeasonTeamTklSoloTFLSacksPDHur
2022Duke000001
2023Duke510000
Career510001

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2022Duke85TEYr 1
2023Duke85TEYr 2
2024Duke85TEYr 3
2025Duke85TEYr 4
2026Duke85TESr. (Yr 5)6′3″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

SeasonTeamPlaysEPA/playPctileMedianTotalUsage
2023Duke80.21––1.7–
2024Duke30.53––1.6–
2025Duke520.8194th (n=1040)0.4641.96%
2026Duke380.4249th (n=829)0.4315.99%

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

2026 Duke 6 games, 21 catches, 250 yards
DateOpponentResultRecYdsTDLong
Sep 5vs.TulaneW 17–⁠3236026
Sep 12atIllinoisW 31–⁠27353035
Sep 19vs.StanfordW 35–⁠7588026
Sep 26vs.William & MaryW 62–⁠7318011
Oct 10atGeorgia TechL 25–⁠28639011
Oct 17vs.North CarolinaL 20–⁠24216011
2025 Duke 13 games, 40 catches, 454 yards, 6 TD
DateOpponentResultRecYdsTDLong
Aug 28vs.ElonW 45–⁠171505
Sep 6vs.IllinoisL 19–⁠451606
Sep 13atTulaneL 27–⁠3421407
Sep 20vs.NC StateW 45–⁠33443021
Sep 27atSyracuseW 38–⁠31505
Oct 18vs.Georgia TechL 18–⁠271909
Nov 1atClemsonW 46–⁠45383056
Nov 8atUConnL 34–⁠37461126
Nov 15vs.VirginiaL 17–⁠34347030
Nov 22atNorth CarolinaW 32–⁠25785127
Nov 29vs.Wake ForestW 49–⁠32427111
Dec 6vs.VirginiaW 27–⁠20319212
Dec 31 ✦vs.Arizona StateW 42–⁠39650114
2024 Duke 2 games, 3 catches, 11 yards, 1 TD
DateOpponentResultRecYdsTDLong
Aug 30vs.ElonW 26–⁠32817
Sep 6vs.NorthwesternW 26–⁠201303
2023 Duke 7 games, 5 tackles
DateOpponentResultRecYdsTDLong
Sep 16vs.NorthwesternW 38–⁠14––––
Sep 23atUConnW 41–⁠71505
Sep 30vs.Notre DameL 14–⁠21––––
Oct 14vs.NC StateW 24–⁠3229121
Oct 21atFlorida StateL 20–⁠38112012
Nov 18atVirginiaL 27–⁠30––––
Dec 23 ✦vs.TroyW 17–⁠101606
2022 Duke 1 game
DateOpponentResultRecYdsTDLong
Nov 4atBoston CollegeW 38–⁠31––––

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.