Running back, Coastal Carolina, 2025–⁠26

Jevon Edwards

Number
No. 20
Height
5′10″
Weight
197 lb
Class (2026)
Sophomore
Hometown
Aiken, SC

Jevon Edwards plays running back for Coastal Carolina. Last time out, against App State: 1 tackles.

2026 so far

141 rushing yards

Last game: 1 tackles vs. App State, L 32–⁠35

Next game: at Georgia State, Oct 31

Game by game this season, rushing yards
  1. 20@WVU
  2. 51FOR
  3. 49@DEL
  4. 17LIB
  5. 4GASO

Filled bars: wins; outlined: losses.

Career highs

80rushing yards, career highvs. Georgia State, 2025

Rushing

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

* The season in progress, so far.

SeasonTeamCarYdsAvgTDLong
2025Coastal Carolina663715.6143
2026Coastal Carolina441413.2020
Career1105124.7143

Receiving

SeasonTeamRecYdsAvgTDLong
2025Coastal Carolina7314.4016
2026Coastal Carolina4358.8014
Career11666.0016

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2025Coastal Carolina20RBFr.
2026Coastal Carolina20RBSo.5′10″197

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/playPctileMedianTotalUsageAdj. rush
2025Coastal Carolina77-0.078th (n=576)0.10-5.59%0.07
2026Coastal Carolina49-0.0714th (n=478)0.10-3.515%0.08

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). Adjusted pass and rush: EPA per play adjusted for the defenses faced (CollegeFootballData’s WEPA). From CollegeFootballData, 2013 on.

Rushing detail

SeasonTeamSuccessLine yardsSecond levelOpen fieldStuffed
2025Coastal Carolina40%2.901.101.3023%
2026Coastal Carolina34%2.500.500.3018%

Where his yards came from, per carry: line yards are the ones credited to the blockers (the first few, and losses), second level the yards 5 to 10 past the line, open field those beyond 10. Success: carries that kept the offense on schedule. Stuffed: carries stopped at or behind the line. From CollegeFootballData, FBS games, 2025 on.

Game by game

2026 Coastal Carolina 6 games, 141 rushing yards
DateOpponentResultCarYdsTDLongRecRec yds
Sep 5atWest VirginiaL 24–⁠3110200818
Sep 12vs.FordhamW 45–⁠795102013
Sep 19atDelawareL 14–⁠22144908––
Sep 24vs.LibertyL 17–⁠3491704224
Oct 3vs.Georgia SouthernL 24–⁠312403––
Oct 16vs.App StateL 32–⁠35––––––
2025 Coastal Carolina 13 games, 371 rushing yards, 1 TD
DateOpponentResultCarYdsTDLongRecRec yds
Aug 30atVirginiaL 7–⁠48160611
Sep 6vs.Charleston SouthernW 13–⁠04703––
Sep 13vs.East CarolinaL 0–⁠3842501415
Sep 20atSouth AlabamaW 38–⁠20551030––
Oct 4atOld DominionL 7–⁠474130728
Oct 11vs.UL MonroeW 23–⁠8648043––
Oct 18atApp StateW 45–⁠37641119––
Oct 30vs.MarshallW 44–⁠27420018––
Nov 8vs.Georgia StateW 40–⁠277800251−2
Nov 15atGeorgia SouthernL 40–⁠45735014––
Nov 22atSouth CarolinaL 7–⁠516706––
Nov 29vs.James MadisonL 10–⁠59320213
Dec 30 ✦vs.Louisiana TechL 14–⁠23936014116

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.