Receiver, Florida (from Georgia Tech), 2023–⁠26

Bailey Stockton

Number
No. 3
Height
5′10″
Weight
183 lb
Class (2026)
Senior
Hometown
Bogart, GA

Bailey Stockton plays receiver for Florida, after Georgia Tech (2023–⁠25). Last time out, at Texas: 4 catches, 31 yards.

2026 so far

27 catches, 289 yards, 2 TD

Last game: 4 catches, 31 yards at Texas, W 27–⁠24

Next game: vs. Georgia, Oct 31

Game by game this season, receiving yards
  1. 20FAU
  2. 41CAM
  3. 12@AUB
  4. 33MISS
  5. 25@MIZ
  6. 127SC
  7. 31@TEX

Filled bars: wins; outlined: losses.

Career highs

8catches, career highvs. South Carolina, 2026127receiving yards, career highvs. South Carolina, 2026

Receiving

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

* The season in progress, so far.

SeasonTeamRecYdsAvgTDLong
2024Georgia Tech1720612.1127
2025Georgia Tech2123311.1033
2026Florida2728910.7259
Career6572811.2359

Returns

SeasonTeamKRYdsTDPRYdsTD
2024Georgia Tech12305570
2025Georgia Tech–––6580
2026Florida–––1160
Career1230121310

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
2023Georgia Tech3WRFr.
2024Georgia Tech3WRSo.
2025Georgia Tech3WRJr.
2026Florida3WRSr.5′10″183

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
2024Georgia Tech171.28––21.7–
2025Georgia Tech280.58––16.25%
2026Florida340.7082nd (n=829)0.4323.97%

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 Florida 7 games, 27 catches, 289 yards, 2 TD
DateOpponentResultRecRec ydsRec TDKRYdsPR
Sep 5vs.Florida AtlanticW 66–⁠213201–––
Sep 12vs.CampbellW 52–⁠34410–––
Sep 19atAuburnW 44–⁠392120–––
Sep 26vs.Ole MissW 52–⁠284330––1
Oct 3atMissouriL 17–⁠452250–––
Oct 10vs.South CarolinaL 19–⁠3881271–––
Oct 17atTexasW 27–⁠244310–––
2025 Georgia Tech 10 games, 21 catches, 233 yards
DateOpponentResultRecRec ydsRec TDKRYdsPR
Aug 29atColoradoW 27–⁠204480–––
Sep 6vs.Gardner-WebbW 59–⁠122430––2
Sep 13vs.ClemsonW 24–⁠21–––––1
Sep 20vs.TempleW 45–⁠243270–––
Sep 27atWake ForestW 30–⁠29120––2
Oct 11vs.Virginia TechW 35–⁠20180–––
Oct 18atDukeW 27–⁠182160–––
Oct 25vs.SyracuseW 41–⁠164480––1
Nov 22vs.PittsburghL 28–⁠422310–––
Nov 28vs.GeorgiaL 9–⁠162100–––
2024 Georgia Tech 11 games, 17 catches, 206 yards, 1 TD
DateOpponentResultRecRec ydsRec TDKRYdsPR
Aug 31vs.Georgia StateW 35–⁠12190–––
Sep 7atSyracuseL 28–⁠312170–––
Sep 14vs.VMIW 59–⁠72240––1
Sep 21atLouisvilleL 19–⁠31–––123–
Oct 5vs.DukeW 24–⁠141180–––
Oct 19vs.Notre DameL 13–⁠312370––1
Oct 26atVirginia TechL 6–⁠21170–––
Nov 9vs.MiamiW 28–⁠231270–––
Nov 21vs.NC StateW 30–⁠295540––1
Nov 29atGeorgiaL 42–⁠44–––––1
Dec 27 ✦vs.VanderbiltL 27–⁠352131––1

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.