Receiver, Nebraska (from UCLA), 2024–⁠26

Kwazi Gilmer

Number
No. 11
Height
6′2″
Weight
190 lb
Class (2026)
Junior
Hometown
Los Angeles, CA

Kwazi Gilmer plays receiver for Nebraska, after UCLA (2024–⁠25). Gilmer is No. 8 in FBS in receiving touchdowns this season. Last time out, at Oregon: 6 catches, 74 yards, 1 TD.

2026 so far

38 catches, 492 yards, 7 TD

No. 8 in FBS in receiving touchdowns

Last game: 6 catches, 74 yards, 1 TD at Oregon, L 14–⁠17

Next game: vs. Washington, Oct 31

Game by game this season, receiving yards
  1. 58OHIO
  2. 39BGSU
  3. 42UND
  4. 101@MSU
  5. 147MD
  6. 31IU
  7. 74@ORE

Filled bars: wins; outlined: losses.

At a glance

Best season
535
Receiving yards, 2025 (UCLA, 3–⁠9)
National rank
No. 8
In FBS in receiving touchdowns, 2026

Career highs

11catches, career highvs. Maryland, 2026147receiving yards, career highvs. Maryland, 20262receiving touchdowns, career hightwice; last vs. Maryland, 2026

Receiving

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

* The season in progress, so far.

SeasonTeamRecYdsAvgTDLong
2024UCLA3134511.1248
2025UCLA5053510.7443
2026Nebraska3849212.9744
Career1191,37211.51348

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2024UCLA11WRFr.
2025UCLA11WRSo.
2026Nebraska11WRJr.6′2″190

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
2024UCLA410.496th (n=581)0.9220.07%
2025UCLA890.2520th (n=1040)0.4622.112%

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 Nebraska 7 games, 38 catches, 492 yards, 7 TD
DateOpponentResultRecYdsTDLongRush
Sep 5vs.OhioW 49–⁠21558121–
Sep 12vs.Bowling GreenW 56–⁠7639213–
Sep 19vs.North DakotaW 34–⁠7342027–
Sep 26atMichigan StateW 31–⁠134101144–
Oct 3vs.MarylandW 48–⁠2311147230–
Oct 10vs.IndianaL 17–⁠20331014–
Oct 17atOregonL 14–⁠17674131–
2025 UCLA 12 games, 50 catches, 535 yards, 4 TD
DateOpponentResultRecYdsTDLongRush
Aug 30vs.UtahL 10–⁠43331014–
Sep 6atUNLVL 23–⁠30887021–
Sep 12vs.New MexicoL 10–⁠35556020–
Sep 27atNorthwesternL 14–⁠17351129–
Oct 4vs.Penn StateW 42–⁠37579143–
Oct 11atMichigan StateW 38–⁠132905–
Oct 18vs.MarylandW 20–⁠17456018–
Oct 25atIndianaL 6–⁠56113013–
Nov 8vs.NebraskaL 21–⁠2821308–
Nov 15atOhio StateL 10–⁠48437118–
Nov 22vs.WashingtonL 14–⁠48330015–
Nov 29atUSCL 10–⁠291073111–
2024 UCLA 10 games, 31 catches, 345 yards, 2 TD
DateOpponentResultRecYdsTDLongRush
Sep 21atLSUL 17–⁠34261032–
Sep 28vs.OregonL 13–⁠34431012–
Oct 5atPenn StateL 11–⁠271303–
Oct 12vs.MinnesotaL 17–⁠212908–
Oct 19atRutgersW 35–⁠32421013–
Nov 2atNebraskaW 27–⁠20388148–
Nov 8vs.IowaW 20–⁠17332020–
Nov 15atWashingtonL 19–⁠3138178
Nov 23vs.USCL 13–⁠19338029–
Nov 30vs.Fresno StateW 20–⁠13654017–

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.