Receiver, Montana State (from Kentucky), 2017–⁠23

Clevan Thomas

Number
No. 2
Height
5′11″
Weight
193 lb
Class (2023)
Senior
Hometown
Miami, FL

Clevan Thomas played receiver at Kentucky (2017–⁠21) and Montana State (2022–⁠23).

Team titles: Big Sky champions, 2022

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2017Kentucky144.004
2018Kentucky36321.0040
2019Kentucky11999.0140
2020Kentucky133.003
2022Montana State2031115.6353
2023Montana State2636414.0439
Career6284413.6853

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2017Kentucky2WRYr 1
2018Kentucky2WRYr 2
2019Kentucky18WRYr 3
2020Kentucky2WRYr 4
2021Kentucky2WRYr 5
2022Montana State2WRYr 6
2023Montana State2WRSr. (Yr 7)5′11″193

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
2017Kentucky1-0.04––0.0–
2018Kentucky31.49––4.5–
2019Kentucky80.14––1.1–
2020Kentucky11.35––1.3–
2022Montana State (FCS)221.00––22.04%
2023Montana State (FCS)271.28––34.55%

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

2023 Montana State 12 games, 26 catches, 364 yards, 4 TD
DateOpponentResultRecYdsTDLongRush
Sep 1vs.Utah TechW 63–⁠20559022–
Sep 9atSouth Dakota StateL 16–⁠201909–
Sep 16vs.StetsonW 57–⁠20242030–
Sep 23atWeber StateW 40–⁠0467020–
Sep 30vs.Portland StateW 38–⁠22120120–
Oct 14vs.Cal PolyW 59–⁠19223017–
Oct 21atSacramento StateW 42–⁠30332018–
Oct 28atIdahoL 21–⁠24323111–
Nov 4vs.Northern ArizonaW 45–⁠21113013–
Nov 11vs.Eastern WashingtonW 57–⁠14115115–
Nov 18atMontanaL 7–⁠37113013–
Dec 2 ✦vs.North Dakota StateL 34–⁠35248139–
2022 Montana State 8 games, 20 catches, 311 yards, 3 TD
DateOpponentResultRecYdsTDLongRush
Sep 10vs.Morehead StateW 63–⁠131818–
Sep 17vs.Oregon StateL 28–⁠68324010−2
Oct 1vs.UC DavisW 41–⁠243621290
Oct 8vs.Idaho StateW 37–⁠6232021–
Oct 15atNorthern ColoradoW 37–⁠141404–
Nov 12atCal PolyW 72–⁠28373053–
Dec 9vs.William & MaryW 55–⁠0334117–
Dec 17 ✦atSouth Dakota StateL 18–⁠39474033–
2020 Kentucky 1 game, 1 catch, 3 yards
DateOpponentResultRecYdsTDLongRush
Oct 3vs.Ole MissL 41–⁠421303–
2019 Kentucky 9 games, 11 catches, 99 yards, 1 TD
DateOpponentResultRecYdsTDLongRush
Sep 21atMississippi StateL 13–⁠281808–
Sep 28atSouth CarolinaL 7–⁠241202–
Oct 12vs.ArkansasW 24–⁠20210110–
Oct 19atGeorgiaL 0–⁠211808–
Oct 26vs.MissouriW 29–⁠71909−5
Nov 9vs.TennesseeL 13–⁠171808–
Nov 16atVanderbiltW 38–⁠14245040–
Nov 30vs.LouisvilleW 45–⁠131404–
Dec 31 ✦vs.Virginia TechW 37–⁠3015054
2018 Kentucky 2 games, 3 catches, 63 yards
DateOpponentResultRecYdsTDLongRush
Sep 1vs.Central MichiganW 35–⁠20112012–
Sep 15vs.Murray StateW 48–⁠10251040–
2017 Kentucky 1 game, 1 catch, 4 yards
DateOpponentResultRecYdsTDLongRush
Sep 2atSouthern MissW 24–⁠171404–

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.