Running back, Charlotte (from App State), 2024–⁠26

Khamani Alexander

Number
No. 5
Height
6′1″
Weight
200 lb
Class (2026)
Sophomore
Hometown
Homestead, FL

Khamani Alexander plays running back for Charlotte, after App State (2024–⁠25). Last time out, at Temple: 9 carries, 20 yards, 1 TD. Alexander leads Charlotte in rushing touchdowns this season.

2026 so far

236 rushing yards, 4 TD

Last game: 9 carries, 20 yards, 1 TD at Temple, W 38–⁠31

Next game: vs. Tulane, Oct 30

Game by game this season, rushing yards
  1. 138CIT
  2. 12@MISS
  3. 18@APP
  4. 8UL
  5. 25MEM
  6. 15@UNT
  7. 20@TEM

Filled bars: wins; outlined: losses.

Career highs

138rushing yards, career highvs. The Citadel, 20262rushing touchdowns, career highat App State, 2026

Rushing

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

* The season in progress, so far.

SeasonTeamCarYdsAvgTDLong
2025App State12504.207
2026Charlotte552364.3466
Career672864.3466

Returns

SeasonTeamKRYdsTD
2025App State183590

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2024App State5RBRS
2025App State5RBFr.
2026Charlotte5RBSo.6′1″200

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
2025App State140.17––2.4––
2026Charlotte660.0638th (n=478)0.103.816%0.13

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
2026Charlotte36%2.200.801.5027%

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 Charlotte 7 games, 236 rushing yards, 4 TD
DateOpponentResultCarRush ydsRush TDKRYds
Sep 5vs.The CitadelL 41–⁠43141381––
Sep 12atOle MissL 9–⁠416120––
Sep 19atApp StateL 21–⁠2613182––
Sep 26vs.LouisianaL 7–⁠34580––
Oct 3vs.MemphisL 8–⁠596250––
Oct 10atNorth TexasL 10–⁠502150––
Oct 17atTempleW 38–⁠319201––
2025 App State 11 games, 18 returns, 359 yards
DateOpponentResultCarRush ydsRush TDKRYds
Aug 29vs.CharlotteW 34–⁠11414019
Sep 6vs.LindenwoodW 20–⁠13–––128
Sep 13atSouthern MissL 22–⁠38–––125
Sep 27atBoise StateL 14–⁠47–––232
Oct 4vs.Oregon StateW 27–⁠23–––489
Oct 11atGeorgia StateW 41–⁠203140––
Oct 18vs.Coastal CarolinaL 37–⁠45–––111
Oct 25atOld DominionL 21–⁠24–––355
Nov 6vs.Georgia SouthernL 23–⁠25–––490
Nov 29vs.Arkansas StateL 29–⁠30–––120
Dec 29 ✦vs.Georgia SouthernL 10–⁠295220––

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.