Running back, Utah State, 2015–18
Eltoro Allen
- Number
- No. 22
- Height
- 5′9″
- Weight
- 185 lb
- Class (2018)
- Senior
- Hometown
- Elk Grove, CA
Eltoro Allen played running back at Utah State (2015–18).
Career highs
103rushing yards, career highvs. Idaho State, 2017Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2017 | Utah State | 68 | 284 | 4.2 | 1 | 18 |
| 2018 | Utah State | 35 | 120 | 3.4 | 1 | 14 |
| Career | 103 | 404 | 3.9 | 2 | 18 | |
Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2017 | Utah State | 8 | 61 | 7.6 | 0 | 17 |
| 2018 | Utah State | 4 | 34 | 8.5 | 0 | 11 |
| Career | 12 | 95 | 7.9 | 0 | 17 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2015 | Utah State | 22 | RB | Fr. | ||
| 2016 | Utah State | 22 | RB | So. | ||
| 2017 | Utah State | 22 | RB | Jr. | ||
| 2018 | Utah State | 22 | RB | Sr. | 5′9″ | 185 |
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 | Adj. rush |
|---|---|---|---|---|---|---|---|---|
| 2017 | Utah State | 84 | -0.07 | 7th (n=287) | 0.12 | -5.6 | 12% | -0.13 |
| 2018 | Utah State | 37 | -0.06 | – | – | -2.2 | 7% | -0.14 |
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.
Game by game
2018 Utah State 7 games, 120 rushing yards, 1 TD
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Aug 31 | at Michigan State | L 31–38 | 3 | 8 | 0 | 3 | 1 | 11 |
| Sep 8 | vs. New Mexico State | W 60–13 | 6 | 30 | 1 | 13 | – | – |
| Oct 5 | at BYU | W 45–20 | 3 | 6 | 0 | 3 | – | – |
| Oct 13 | vs. UNLV | W 59–28 | 5 | 8 | 0 | 5 | 1 | 9 |
| Oct 27 | vs. New Mexico | W 61–19 | 9 | 18 | 0 | 12 | 1 | 4 |
| Nov 3 | at Hawai’i | W 56–17 | 7 | 39 | 0 | 14 | – | – |
| Nov 10 | vs. San José State | W 62–24 | 2 | 11 | 0 | 7 | 1 | 10 |
2017 Utah State 9 games, 284 rushing yards, 1 TD
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 1 | at Wisconsin | L 10–59 | 2 | −3 | 0 | 1 | 1 | 11 |
| Sep 7 | vs. Idaho State | W 51–13 | 19 | 103 | 1 | 16 | 1 | 2 |
| Sep 16 | at Wake Forest | L 10–46 | 13 | 20 | 0 | 8 | – | – |
| Sep 23 | atSan José State | W 61–10 | 18 | 89 | 0 | 17 | – | – |
| Sep 29 | vs.BYU | W 40–24 | 6 | 10 | 0 | 4 | – | – |
| Oct 7 | vs. Colorado State | L 14–27 | 4 | 18 | 0 | 11 | 5 | 45 |
| Oct 14 | vs. Wyoming | L 23–28 | 1 | 15 | 0 | 15 | – | – |
| Oct 21 | atUNLV | W 52–28 | 4 | 26 | 0 | 18 | – | – |
| Oct 28 | vs. Boise State | L 14–41 | 1 | 6 | 0 | 6 | 1 | 3 |
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.