Running back, Missouri State, 2022–23
Celdon Manning
- Number
- No. 31
- Height
- 5′10″
- Weight
- 190 lb
- Class (2023)
- Sophomore
- Hometown
- Allen, TX
Celdon Manning played running back at Missouri State (2022–23).
Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2022 | Missouri State | 19 | 134 | 7.1 | 0 | 28 |
| 2023 | Missouri State | 21 | 151 | 7.2 | 1 | 32 |
| Career | 40 | 285 | 7.1 | 1 | 32 | |
Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2022 | Missouri State | 12 | 187 | 15.6 | 1 | 64 |
| 2023 | Missouri State | 9 | 107 | 11.9 | 1 | 23 |
| Career | 21 | 294 | 14.0 | 2 | 64 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2022 | Missouri State | 31 | RB | Fr. | ||
| 2023 | Missouri State | 31 | RB | So. | 5′10″ | 190 |
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 |
|---|---|---|---|---|---|---|---|
| 2022 | Missouri State (FCS) | 27 | 0.68 | – | – | 18.4 | 5% |
| 2023 | Missouri State (FCS) | 30 | 0.63 | – | – | 18.9 | 6% |
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 Missouri State 8 games, 151 rushing yards, 1 TD
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Sep 1 | at Kansas | L 17–48 | 1 | 3 | 0 | 2 | 31 | 0 |
| Sep 9 | at UT Martin | L 31–38 | 2 | 18 | 0 | 2 | 24 | 0 |
| Sep 23 | vs. Utah Tech | W 59–14 | 5 | 14 | 0 | 1 | 16 | 1 |
| Sep 30 | at Southern Illinois | L 20–33 | 2 | 9 | 0 | – | – | – |
| Oct 7 | vs. North Dakota State | L 10–38 | – | – | – | 1 | 5 | 0 |
| Nov 4 | vs. Illinois State | L 35–36 | 3 | 43 | 1 | 1 | 17 | 0 |
| Nov 11 | vs. Northern Iowa | W 35–16 | 5 | 23 | 0 | 1 | 3 | 0 |
| Nov 18 | at South Dakota State | L 17–35 | 3 | 41 | 0 | 1 | 11 | 0 |
2022 Missouri State 10 games, 12 catches, 187 yards, 1 TD
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Sep 1 | at Central Arkansas | W 27–14 | 1 | 8 | 0 | – | – | – |
| Sep 8 | vs.UT Martin | W 35–30 | 6 | 36 | 0 | 2 | 71 | 1 |
| Sep 17 | at Arkansas | L 27–38 | 1 | 1 | 0 | 1 | 9 | 0 |
| Sep 24 | vs.South Dakota State | L 14–28 | – | – | – | 1 | 3 | 0 |
| Oct 1 | at North Dakota | L 31–48 | – | – | – | 1 | 18 | 0 |
| Oct 22 | atNorthern Iowa | L 20–41 | – | – | – | 1 | 12 | 0 |
| Oct 29 | vs. Western Illinois | W 64–14 | 2 | 19 | 0 | 4 | 68 | 0 |
| Nov 5 | at South Dakota | L 13–20 | 1 | 5 | 0 | 1 | 5 | 0 |
| Nov 12 | vs. Youngstown State | W 25–22 | 5 | 49 | 0 | – | – | – |
| Nov 19 | at Indiana State | W 24–7 | 3 | 16 | 0 | 1 | 1 | 0 |
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.