Receiver, Bucknell, 2022–⁠25

Josh Gary

Number
No. 3
Height
5′11″
Weight
210 lb
Class (2025)
Senior
Hometown
Upper Marlboro, MD

Josh Gary played receiver at Bucknell (2022–⁠25).

Career highs

13catches, career highat Pennsylvania, 2024139receiving yards, career highat Colgate, 20232receiving touchdowns, career highat VMI, 2024

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2022Bucknell1616510.3022
2023Bucknell3137112.0249
2024Bucknell5364512.2443
2025Bucknell353259.3125
Career1351,50611.2749

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2022Bucknell3WRFr.
2023Bucknell3WRSo.
2024Bucknell3WRJr.
2025Bucknell3WRSr.5′11″210

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
2022Bucknell (FCS)71.27––8.9–
2023Bucknell (FCS)380.8354th (n=681)0.8031.75%
2024Bucknell (FCS)700.7325th (n=581)0.9251.49%
2025Bucknell (FCS)570.2823rd (n=1040)0.4615.88%

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 Bucknell 12 games, 35 catches, 325 yards, 1 TD
DateOpponentResultRecYdsTDLongRush
Aug 30atAir ForceL 13–⁠491606–
Sep 6atMaristW 34–⁠23327013–
Sep 13vs.VMIW 35–⁠28325010–
Sep 20vs.LehighL 24–⁠41453017–
Sep 27vs.Saint FrancisW 30–⁠23225013–
Oct 4vs.RichmondW 33–⁠28338025–
Oct 11atLafayetteL 24–⁠622170116
Oct 18atCornellL 20–⁠30334015–
Oct 25vs.GeorgetownL 24–⁠31216012–
Nov 8atFordhamW 37–⁠19315052
Nov 15vs.Holy CrossL 20–⁠37649014–
Nov 22atColgateL 19–⁠3832018–
2024 Bucknell 12 games, 53 catches, 645 yards, 4 TD
DateOpponentResultRecYdsTDLongRush
Aug 31atNavyL 21–⁠4921509–
Sep 7atVMIW 35–⁠28354241−1
Sep 14vs.MerrimackL 21–⁠31317110–
Sep 21vs.MaristW 34–⁠18228022–
Sep 28atLehighW 38–⁠351505–
Oct 12atPennsylvaniaL 21–⁠3113137018–
Oct 19vs.CornellL 21–⁠34357024–
Oct 26atGeorgetownL 20–⁠21591043–
Nov 2vs.LafayetteW 21–⁠14671023–
Nov 9vs.FordhamW 28–⁠27797026–
Nov 16atHoly CrossL 38–⁠40322010–
Nov 23vs.ColgateW 48–⁠34551115–
2023 Bucknell 10 games, 31 catches, 371 yards, 2 TD
DateOpponentResultRecYdsTDLongRush
Sep 2atJames MadisonL 3–⁠38216014–
Sep 9vs.VMIW 21–⁠131303–
Sep 23vs.PennsylvaniaL 21–⁠37113113–
Sep 30atLafayetteL 22–⁠56676025–
Oct 7vs.Holy CrossL 27–⁠551303–
Oct 14atCornellW 21–⁠13243032–
Oct 21vs.LehighL 18–⁠27335023–
Oct 28atColgateW 49–⁠349139149–
Nov 4atFordhamL 21–⁠27538011–
Nov 11vs.GeorgetownL 47–⁠501505–
2022 Bucknell 10 games, 16 catches, 165 yards
DateOpponentResultRecYdsTDLongRush
Sep 3vs.TowsonL 13–⁠1421307–
Sep 17atCentral MichiganL 0–⁠41231018–
Oct 1vs.LafayetteL 14–⁠24341022–
Oct 8atHoly CrossL 0–⁠57112012–
Oct 15atYaleL 9–⁠291606–
Oct 22atLehighW 19–⁠17215012–
Oct 29vs.ColgateL 7–⁠131303–
Nov 5vs.FordhamL 17–⁠59–––––
Nov 12atGeorgetownW 24–⁠21335013–
Nov 19vs.MaristW 24–⁠131909–

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.