Running back, Miami, 2010–⁠13

Eduardo Clements

Number
No. 23
Height
5′10″
Hometown
Miami, FL

Eduardo Clements played running back at Miami (2010–⁠13).

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2010Miami8324.0011
2011Miami15825.5122
2012*Miami16704.4217
2013*Miami301946.5028
Career693785.5328

Returns

SeasonTeamKRYdsTD
2010Miami101950

Receiving

SeasonTeamRecYdsAvgTDLong
2010Miami199.009
2011Miami1416311.6024
2012*Miami2115.506
Career1718310.8024

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.

Defense before 2016

SeasonGSoloAstTkl
20108325
201111729
20126404
2013N11123
On file15621

Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources, marked by season: unmarked, cfbstats.com (Open Data Commons Attribution License), its game lines summed (G: the games he has a line in); N, NCAA statistics, via octonion/football, the season’s official lines (G: games played). A dash: the source has no number for it.

On the roster

SeasonTeamNo.PosHt
2010Miami23RB
2011Miami23RB
2012Miami23RB
2013Miami23RB5′10″

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

SeasonTeamPlaysEPA/playPctileMedianTotalUsage
2013Miami310.16––5.07%

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

2013 Miami 7 games, 194 rushing yards
DateOpponentResultCarRush ydsRush TDKRYds
Aug 30vs.Florida AtlanticW 34–⁠66230––
Sep 21vs.Savannah StateW 77–⁠711750––
Oct 17atNorth CarolinaW 27–⁠232270––
Nov 2atFlorida StateL 14–⁠41110––
Nov 16atDukeL 30–⁠481280––
Nov 23vs.VirginiaW 45–⁠264200––
Nov 29atPittsburghW 41–⁠315200––
2012 Miami 6 games, 70 rushing yards, 2 TD
DateOpponentResultCarRush ydsRush TDKRYds
Sep 1atBoston CollegeW 41–⁠32341––
Sep 8atKansas StateL 13–⁠52410––
Sep 15vs.Bethune-CookmanW 38–⁠105371––
Sep 22atGeorgia TechW 42–⁠36140––
Sep 29vs.NC StateW 44–⁠37140––
Oct 6vs.Notre DameL 3–⁠412200––
2011 Miami 9 games, 14 catches, 163 yards
DateOpponentResultCarRush ydsRush TDKRYds
Oct 1vs.Bethune-CookmanW 45–⁠144371––
Oct 8atVirginia TechL 35–⁠38–––––
Oct 15atNorth CarolinaW 30–⁠24130––
Oct 22vs.Georgia TechW 24–⁠7–––––
Oct 27vs.VirginiaL 21–⁠28–––––
Nov 5vs.DukeW 49–⁠145300––
Nov 12atFlorida StateL 19–⁠23270––
Nov 19atSouth FloridaW 6–⁠3350––
Nov 25vs.Boston CollegeL 17–⁠24–––––
2010 Miami 8 games, 10 returns, 195 yards
DateOpponentResultCarRush ydsRush TDKRYds
Sep 2vs.Florida A&MW 45–⁠06230––
Sep 11atOhio StateL 24–⁠36–––114
Oct 2atClemsonW 30–⁠21–––124
Oct 9vs.Florida StateL 17–⁠45290112
Oct 16atDukeW 28–⁠13–––121
Oct 23vs.North CarolinaW 33–⁠10–––129
Nov 20vs.Virginia TechL 17–⁠31–––242
Nov 27vs.South FloridaL 20–⁠23–––353

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.