Receiver, Bucknell, 2023–⁠26

T.J. Cadden

Number
No. 21
Height
6′0″
Weight
195 lb
Class (2026)
Senior
Hometown
Phoenixville, PA

T.J. Cadden plays receiver for Bucknell. Last time out, at Georgetown: 5 catches, 77 yards.

2026 so far

16 catches, 162 yards

Last game: 5 catches, 77 yards at Georgetown, L 14–⁠21

Next game: at Holy Cross, Oct 24

Game by game this season, receiving yards
  1. 52VILL
  2. 33@PITT
  3. 77@GTWN

Filled bars: wins; outlined: losses.

Career highs

7catches, career hightwice; last vs. Villanova, 2026123receiving yards, career highvs. VMI, 20252receiving touchdowns, career highat Lafayette, 2025

Receiving

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

* The season in progress, so far.

SeasonTeamRecYdsAvgTDLong
2023Bucknell3258.3012
2024Bucknell2737814.0337
2025Bucknell4558913.1659
2026Bucknell1616210.1027
Career911,15412.7959

Returns

SeasonTeamKRYdsTDPRYdsTD
2023Bucknell3450190
2024Bucknell133330182381
2025Bucknell285700161950
2026Bucknell612404760
Career501,0720395181

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2023Bucknell21WRFr.
2024Bucknell21WRSo.
2025Bucknell21WRJr.
2026Bucknell21WRSr.6′0″195

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
2025Bucknell (FCS)840.5668th (n=1040)0.4647.411%
2026Bucknell (FCS)260.4552nd (n=829)0.4311.611%

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 Bucknell 4 games, 16 catches, 162 yards
DateOpponentResultRecRec ydsRec TDKRYdsPR
Aug 29atRichmondL 14–⁠35–––––1
Sep 5vs.VillanovaL 16–⁠1775202533
Sep 26atPittsburghL 0–⁠594330350–
Oct 10atGeorgetownL 14–⁠215770121–
2025 Bucknell 12 games, 45 catches, 589 yards, 6 TD
DateOpponentResultRecRec ydsRec TDKRYdsPR
Aug 30atAir ForceL 13–⁠492210122–
Sep 6atMaristW 34–⁠23–––3552
Sep 13vs.VMIW 35–⁠28512312511
Sep 20vs.LehighL 24–⁠414361114–
Sep 27vs.Saint FrancisW 30–⁠23678151062
Oct 4vs.RichmondW 33–⁠284250250–
Oct 11atLafayetteL 24–⁠6251082123–
Oct 18atCornellL 20–⁠305680236–
Oct 25vs.GeorgetownL 24–⁠3157614593
Nov 8atFordhamW 37–⁠192601192
Nov 15vs.Holy CrossL 20–⁠3742802173
Nov 22atColgateL 19–⁠38320041183
2024 Bucknell 9 games, 27 catches, 378 yards, 3 TD
DateOpponentResultRecRec ydsRec TDKRYdsPR
Aug 31atNavyL 21–⁠4959701521
Sep 7atVMIW 35–⁠286871––4
Sep 14vs.MerrimackL 21–⁠31–––1212
Sep 21vs.MaristW 34–⁠1833012472
Sep 28atLehighW 38–⁠35121021172
Oct 12atPennsylvaniaL 21–⁠313240352–
Oct 19vs.CornellL 21–⁠3478412281
Oct 26atGeorgetownL 20–⁠2111302164
Nov 2vs.LafayetteW 21–⁠141220––2
2023 Bucknell 4 games, 3 catches, 25 yards
DateOpponentResultRecRec ydsRec TDKRYdsPR
Sep 30atLafayetteL 22–⁠561110–––
Oct 21vs.LehighL 18–⁠27–––2451
Oct 28atColgateW 49–⁠34–––10–
Nov 18atMaristW 38–⁠212140–––

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.