Running back, Indiana State, 2017–19
Titus McCoy
- Number
- No. 30
- Height
- 5′10″
- Weight
- 187 lb
- Hometown
- Ewa Beach, HI
Titus McCoy played running back at Indiana State (2017–19).
Career highs
88rushing yards, career highat Kansas, 2019Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2017 | Indiana State | 2 | −6 | −3.0 | 0 | 0 |
| 2018* | Indiana State | 14 | 38 | 2.7 | 1 | 9 |
| 2019 | Indiana State | 14 | 88 | 6.3 | 0 | 19 |
| Career | 30 | 120 | 4.0 | 1 | 19 | |
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 | Ht | Wt |
|---|---|---|---|---|---|
| 2017 | Indiana State | 30 | RB | ||
| 2018 | Indiana State | 30 | RB | ||
| 2019 | Indiana State | 30 | RB | 5′10″ | 187 |
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 |
|---|---|---|---|---|---|---|---|
| 2017 | Indiana State (FCS) | 2 | -0.56 | – | – | -1.1 | – |
| 2019 | Indiana State (FCS) | 14 | 0.14 | – | – | 2.0 | – |
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
2019 Indiana State 1 game, 88 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Aug 31 | at Kansas | L 17–24 | 14 | 88 | 0 | 19 |
No box score in the source for Sep 7 vs. Dayton; Sep 14 vs. Eastern Kentucky; Sep 21 vs. Eastern Illinois; Oct 5 at South Dakota; Oct 12 vs. Western Illinois; Oct 19 vs. South Dakota State; Oct 26 at Illinois State; Nov 2 vs. Southern Illinois; Nov 9 at Northern Iowa; Nov 16 vs. Youngstown State; Nov 23 at Missouri State, so those games are not listed.
2018 Indiana State 1 game, 38 rushing yards, 1 TD
| Date | Opponent | Result | Car | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 8 | at Louisville | L 7–31 | 14 | 38 | 1 | 9 |
No box score in the source for Aug 30 vs. Quincy; Sep 15 at Eastern Illinois; Sep 27 vs. Northern Iowa; Oct 6 at South Dakota State; Oct 13 vs. Missouri State; Oct 20 at Southern Illinois; Oct 27 at Youngstown State; Nov 3 vs. South Dakota; Nov 10 vs. Illinois State; Nov 17 at Western Illinois, so those games are not listed.
2017 Indiana State 1 game, −6 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 9 | at Tennessee | L 7–42 | 2 | −6 | 0 | 0 |
No box score in the source for Aug 31 vs. Eastern Illinois; Sep 16 at Liberty; Sep 30 at Illinois State; Oct 7 vs. North Dakota State; Oct 14 at South Dakota; Oct 21 vs. Southern Illinois; Oct 28 at Missouri State; Nov 4 vs. Youngstown State; Nov 11 vs. Western Illinois; Nov 18 at Northern Iowa, 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.