Running back, Presbyterian (from Western Carolina), 2020–22
Mikai Stanley
- Number
- No. 36
- Height
- 6′2″
- Weight
- 240 lb
- Class (2022)
- Junior
- Hometown
- Wilmington, NC
Mikai Stanley played running back at Western Carolina (2020–21) and Presbyterian (2022).
Career highs
2rushing touchdowns, career highvs. Davidson, 2022Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2020* | Western Carolina | 13 | 52 | 4.0 | 0 | 16 |
| 2021* | Western Carolina | 5 | 17 | 3.4 | 0 | 7 |
| 2022 | Presbyterian | 31 | 147 | 4.7 | 2 | 61 |
| Career | 49 | 216 | 4.4 | 2 | 61 | |
Season lines from CollegeFootballData, regular season and bowls. * That team-season’s player lines are missing part of the team’s yards in our source, so these numbers may be short.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2020 | Western Carolina | 36 | RB | Fr. | ||
| 2021 | Western Carolina | 36 | RB | So. | ||
| 2022 | Presbyterian | 36 | RB | Jr. | 6′2″ | 240 |
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 |
|---|---|---|---|---|---|---|---|
| 2020 | Western Carolina (FCS) | 13 | -0.31 | – | – | -4.1 | – |
| 2021 | Western Carolina (FCS) | 5 | -0.12 | – | – | -0.6 | – |
| 2022 | Presbyterian (FCS) | 13 | 0.18 | – | – | 2.3 | – |
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
2022 Presbyterian 6 games, 147 rushing yards, 2 TD
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 3 | at Austin Peay | L 0–63 | 6 | 9 | 0 | 4 | – | – |
| Sep 10 | vs.Virginia Lynchburg | W 21–13 | 6 | 33 | 0 | 9 | 1 | 14 |
| Sep 17 | at Western Carolina | L 21–77 | 6 | 20 | 0 | 10 | – | – |
| Sep 24 | vs. Davidson | L 24–56 | 7 | 74 | 2 | 61 | – | – |
| Oct 1 | at Morehead State | L 10–14 | 3 | 1 | 0 | 1 | – | – |
| Oct 8 | vs. Valparaiso | L 21–41 | 3 | 10 | 0 | 8 | – | – |
2021 Western Carolina 1 game, 17 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 11 | at Oklahoma | L 0–76 | 5 | 17 | 0 | 7 | – | – |
No box score in the source for Sep 4 vs. Eastern Kentucky, so that game is not listed.
2020 Western Carolina 2 games, 52 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Nov 14 | at Liberty | L 14–58 | 2 | 6 | 0 | 5 | – | – |
| Dec 5 | at North Carolina | L 9–49 | 11 | 46 | 0 | 16 | – | – |
No box score in the source for Nov 21 at Eastern Kentucky; Feb 20 at Furman; Feb 27 at Samford; Mar 6 vs. VMI; Mar 13 vs. The Citadel; Mar 20 at Mercer; Mar 27 at East Tennessee State, so those games are not listed.
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.