Running back, Coastal Carolina (from Lafayette), 2023–26
Kente Edwards
- Number
- No. 21
- Height
- 5′9″
- Weight
- 197 lb
- Class (2026)
- Freshman
- Hometown
- Annandale, NJ
Kente Edwards plays running back for Coastal Carolina, after Lafayette (2023–25).
2026 so far
21 rushing yards
Last game: vs. Fordham, W 45–7
Next game: at Georgia State, Oct 31
Career highs
265rushing yards, career highat Richmond, 20254rushing touchdowns, career highat Georgetown, 2025Team titles: Patriot League champions, 2023
Rushing
* The season in progress, so far.
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2023 | Lafayette | 8 | 42 | 5.3 | 1 | 12 |
| 2024 | Lafayette | 8 | 68 | 8.5 | 0 | 20 |
| 2025 | Lafayette | 199 | 1,454 | 7.3 | 20 | 78 |
| 2026 | Coastal Carolina | 4 | 21 | 5.3 | 0 | 11 |
| Career | 219 | 1,585 | 7.2 | 21 | 78 | |
Receiving
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2023 | Lafayette | 21 | RB | Yr 1 | ||
| 2024 | Lafayette | 21 | RB | Yr 2 | ||
| 2025 | Lafayette | 21 | RB | Yr 3 | ||
| 2026 | Coastal Carolina | 21 | RB | Fr. (Yr 4) | 5′9″ | 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
| Season | Team | Plays | EPA/play | Pctile | Median | Total | Usage |
|---|---|---|---|---|---|---|---|
| 2025 | Lafayette (FCS) | 204 | 0.32 | 96th (n=576) | 0.10 | 64.7 | 30% |
| 2026 | Coastal Carolina | 3 | 0.14 | – | – | 0.4 | – |
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 Coastal Carolina 1 game, 21 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 12 | vs. | W 45–7 | 4 | 21 | 0 | 11 | – | – |
2025 Lafayette 10 games, 1,454 rushing yards, 20 TD
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Aug 28 | at | L 7–26 | 10 | 27 | 0 | 6 | 1 | 7 |
| Sep 6 | at | W 42–26 | 12 | 127 | 3 | 78 | – | – |
| Sep 13 | at | W 42–37 | 19 | 255 | 4 | 70 | – | – |
| Sep 19 | vs. | W 38–14 | 25 | 150 | 3 | 14 | – | – |
| Sep 27 | vs. | L 28–38 | 5 | 26 | 0 | 11 | 2 | 7 |
| Oct 18 | at | L 13–45 | 13 | 41 | 0 | 9 | 3 | 26 |
| Nov 1 | at | W 21–13 | 28 | 146 | 2 | 27 | 3 | 22 |
| Nov 8 | vs. | W 59–42 | 20 | 260 | 3 | 49 | 1 | 5 |
| Nov 15 | at | W 35–28 | 26 | 265 | 2 | 70 | – | – |
| Nov 22 | vs. | L 32–42 | 41 | 157 | 3 | 19 | – | – |
2024 Lafayette 3 games, 68 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 14 | vs. | W 56–14 | 3 | 40 | 0 | 20 | – | – |
| Oct 12 | vs. | L 0–17 | – | – | – | – | – | – |
| Nov 16 | vs. | W 42–10 | 5 | 28 | 0 | 11 | – | – |
2023 Lafayette 2 games, 42 rushing yards, 1 TD
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.
