Receiver, Florida State, 2018–⁠22

Keyshawn Helton

Lettered 2018–⁠19, 2021 (school media guide)

Number
No. 6
Height
5′9″
Weight
175 lb
Class (2022)
Senior
Hometown
Pensacola, FL

Keyshawn Helton played receiver at Florida State (2018–⁠22).

Career highs

7catches, career highvs. Louisville, 2019100receiving yards, career highvs. Clemson, 2018

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2018Florida State1117616.0173
2019Florida State1723914.1358
2020Florida State141198.5241
2021Florida State1928515.0244
Career6181913.4873

Returns

SeasonTeamKRYdsTDPRYdsTD
2018Florida State91960–––
2019Florida State102280–––
2020Florida State513005260
2021Florida State–––8320
Career24554013580

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
2018Florida State6WRYr 1
2019Florida State6WRYr 2
2020Florida State6WRYr 3
2021Florida State6WRYr 4
2022Florida State6WRSr. (Yr 5)5′9″175

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
2018Florida State160.64––10.2–
2019Florida State230.75––17.37%
2020Florida State240.07––1.65%
2021Florida State241.19––28.75%

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

2021 Florida State 10 games, 19 catches, 285 yards, 2 TD
DateOpponentResultRecRec ydsRec TDKRYdsPR
Sep 5vs.Notre DameL 38–⁠414530–––
Sep 11vs.Jacksonville StateL 17–⁠20–––––3
Sep 18atWake ForestL 14–⁠351120––1
Sep 25vs.LouisvilleL 23–⁠31–––––1
Oct 2vs.SyracuseW 33–⁠302261–––
Oct 9atNorth CarolinaW 35–⁠253710–––
Oct 23vs.MassachusettsW 59–⁠31200––1
Oct 30atClemsonL 20–⁠303450–––
Nov 6vs.NC StateL 14–⁠284491––2
Nov 27atFloridaL 21–⁠24190–––
2020 Florida State 8 games, 14 catches, 119 yards, 2 TD
DateOpponentResultRecRec ydsRec TDKRYdsPR
Sep 12vs.Georgia TechL 13–⁠16131–––
Sep 26atMiamiL 10–⁠52120–––
Oct 3vs.Jacksonville StateW 41–⁠24353141093
Oct 17vs.North CarolinaW 31–⁠282430–––
Oct 24atLouisvilleL 16–⁠48–––1211
Nov 7vs.PittsburghL 17–⁠41350–––
Nov 14atNC StateL 22–⁠384130–––
Dec 12vs.DukeW 56–⁠35–––––1
2019 Florida State 6 games, 17 catches, 239 yards, 3 TD
DateOpponentResultRecRec ydsRec TDKRYdsPR
Aug 31vs.Boise StateL 31–⁠361581117–
Sep 7vs.UL MonroeW 45–⁠44–––5135–
Sep 14atVirginiaL 24–⁠315341–––
Sep 21vs.LouisvilleW 35–⁠247961318–
Sep 28vs.NC StateW 31–⁠133440158–
Oct 12atClemsonL 14–⁠45170–––
2018 Florida State 6 games, 11 catches, 176 yards, 1 TD
DateOpponentResultRecRec ydsRec TDKRYdsPR
Oct 20vs.Wake ForestW 38–⁠17230–––
Oct 27vs.ClemsonL 10–⁠5931001–––
Nov 3atNC StateL 28–⁠47–––489–
Nov 10atNotre DameL 13–⁠42–––242–
Nov 17vs.Boston CollegeW 22–⁠216730248–
Nov 24vs.FloridaL 14–⁠41–––117–

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.