Running back, Chattanooga, 2014–16
Richardre Bagley
- Number
- No. 23
- Height
- 5′9″
- Weight
- 180 lb
- Hometown
- Ewa Beach, HI
Richardre Bagley played running back at Chattanooga (2014–16).
Team titles: Southern champions, 2014 and 2015
Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2014 | Chattanooga | 3 | 25 | 8.3 | 0 | 14 |
| 2015 | Chattanooga | 3 | 10 | 3.3 | 0 | 4 |
| 2016 | Chattanooga | 5 | 14 | 2.8 | 0 | 8 |
| Career | 11 | 49 | 4.5 | 0 | 14 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Ht | Wt |
|---|---|---|---|---|---|
| 2014 | Chattanooga | 23 | RB | ||
| 2015 | Chattanooga | 23 | RB | ||
| 2016 | Chattanooga | 23 | RB | 5′9″ | 180 |
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 |
|---|---|---|---|---|---|---|---|
| 2014 | Chattanooga (FCS) | 8 | 0.23 | – | – | 1.8 | – |
| 2015 | Chattanooga (FCS) | 6 | -0.15 | – | – | -0.9 | – |
| 2016 | Chattanooga (FCS) | 10 | 0.05 | – | – | 0.5 | – |
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
2016 Chattanooga 1 game, 35 rushing yards
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Nov 19 | at Alabama | L 3–31 | 5 | 14 | 0 | 8 | 35 |
No box score in the source for Sep 1 vs. Shorter; Sep 10 vs. Presbyterian; Sep 17 at Furman; Sep 24 vs. Samford; Oct 1 at East Tennessee State; Oct 8 vs. Mercer; Oct 15 at The Citadel; Oct 22 vs. VMI; Oct 29 at Western Carolina; Nov 12 vs. Wofford; Nov 26 vs. Weber State; Dec 3 at Sam Houston, so those games are not listed.
2015 Chattanooga 1 game, 17 rushing yards
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Nov 21 | at Florida State | L 13–52 | 3 | 10 | 0 | 4 | 17 |
No box score in the source for Sep 5 vs. Jacksonville State; Sep 12 vs. Mars Hill; Sep 19 at Samford; Sep 26 at Presbyterian; Oct 10 vs. Furman; Oct 17 at VMI; Oct 24 at Wofford; Oct 31 vs. Western Carolina; Nov 7 at Mercer; Nov 14 vs. The Citadel; Nov 28 vs. Fordham; Dec 5 at Jacksonville State, so those games are not listed.
2014 Chattanooga 2 games, 22 rushing yards, 1 TD
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Aug 28 | at Central Michigan | L 16–20 | 2 | 18 | 0 | 14 | – |
| Oct 11 | at Tennessee | L 10–45 | 1 | 7 | 0 | 7 | 22 |
No box score in the source for Sep 6 vs. Jacksonville State; Sep 13 at Austin Peay; Sep 27 vs. Samford; Oct 4 vs. VMI; Oct 18 at The Citadel; Oct 25 vs. Mercer; Nov 1 at Western Carolina; Nov 8 vs. Wofford; Nov 15 at Tennessee Tech; Nov 22 at Furman; Dec 6 vs. Indiana State; Dec 13 at New Hampshire, 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.