Receiver, Lafayette, 2024–⁠26

Mason Kuehner

Number
No. 8
Height
5′11″
Weight
186 lb
Class (2026)
Junior
Hometown
Nazareth, PA

Mason Kuehner plays receiver for Lafayette. Last time out, at Bucknell: 6 catches, 55 yards. Kuehner leads Lafayette in receiving yards and receiving touchdowns this season.

2026 so far

33 catches, 465 yards, 3 TD

Last game: 6 catches, 55 yards at Bucknell, W 20–⁠7

Next game: at Fordham, Oct 24

Game by game this season, receiving yards
  1. 12@CONN
  2. 80MRST
  3. 58@COLU
  4. 152HC
  5. 108RICH
  6. 55@BUCK

Filled bars: wins; outlined: losses.

Career highs

11catches, career highvs. Lehigh, 2025152receiving yards, career highvs. Holy Cross, 20263receiving touchdowns, career highvs. Holy Cross, 2026

Receiving

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

* The season in progress, so far.

SeasonTeamRecYdsAvgTDLong
2024Lafayette1725815.2169
2025Lafayette5257211.0144
2026Lafayette3346514.1343
Career1021,29512.7569

Returns

SeasonTeamKRYdsTDPRYdsTD
2024Lafayette2150151911
2025Lafayette–––9480
2026Lafayette–––5400
Career2150292791

Season lines from CollegeFootballData, regular season and bowls. A dash: the source has no number for that season (often an FCS season), and career totals count only the numbers on file.

On the roster

SeasonTeamNo.PosClassHtWt
2024Lafayette8WRFr.
2025Lafayette8WRSo.
2026Lafayette8WRJr.5′11″186

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
2025Lafayette (FCS)770.3635th (n=1040)0.4627.910%
2026Lafayette (FCS)600.3134th (n=829)0.4318.615%

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 Lafayette 6 games, 33 catches, 465 yards, 3 TD
DateOpponentResultRecRec ydsRec TDKRYdsPR
Sep 5atUConnL 7–⁠562120–––
Sep 12vs.MaristW 13–⁠94800–––
Sep 19atColumbiaL 34–⁠406580–––
Sep 26vs.Holy CrossL 30–⁠38101523––2
Oct 3vs.RichmondL 31–⁠4051080–––
Oct 17atBucknellW 20–⁠76550––3
2025 Lafayette 12 games, 52 catches, 572 yards, 1 TD
DateOpponentResultRecRec ydsRec TDKRYdsPR
Aug 28atBowling GreenL 7–⁠263170–––
Sep 6atStonehillW 42–⁠261110––1
Sep 13atGeorgetownW 42–⁠374860–––
Sep 19vs.ColumbiaW 38–⁠143580––1
Sep 27vs.PrincetonL 28–⁠384610––2
Oct 4vs.FordhamW 24–⁠105440––1
Oct 11vs.BucknellW 62–⁠247620––2
Oct 18atOregon StateL 13–⁠452280––1
Nov 1atHoly CrossW 21–⁠136510–––
Nov 8vs.ColgateW 59–⁠424491–––
Nov 15atRichmondW 35–⁠28260–––
Nov 22vs.LehighL 32–⁠4211990––1
2024 Lafayette 9 games, 17 catches, 258 yards, 1 TD
DateOpponentResultRecRec ydsRec TDKRYdsPR
Sep 7atMonmouthW 40–⁠35–––2151
Sep 14vs.MaristW 56–⁠14–––––3
Sep 21atColumbiaL 20–⁠314721––1
Oct 12vs.GeorgetownL 0–⁠171340––2
Oct 19vs.Sacred HeartW 31–⁠17–––––3
Oct 26vs.Holy CrossL 28–⁠34280––1
Nov 2atBucknellL 14–⁠217540–––
Nov 9atColgateW 21–⁠20–––––1
Nov 16vs.StonehillW 42–⁠103900––3

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.