Running back, Eastern Michigan, 2014–⁠18

Ian Eriksen

Number
No. 25
Height
5′10″
Weight
207 lb
Class (2018)
Senior
Hometown
Clarkston, MI

Ian Eriksen played running back at Eastern Michigan (2014–⁠18).

Career highs

171rushing yards, career highvs. Northern Illinois, 20163rushing touchdowns, career hightwice; last at Kent State, 2018

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2016Eastern Michigan1847714.2931
2017Eastern Michigan1798054.5871
2018Eastern Michigan803614.5445
Career4431,9374.42171

Receiving

SeasonTeamRecYdsAvgTDLong
2016Eastern Michigan2124311.6032
2017Eastern Michigan161197.4026
2018Eastern Michigan5214.2013
Career423839.1032

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2014Eastern Michigan25RBRS
2015Eastern Michigan25RBFr.
2016Eastern Michigan25RBSo.
2017Eastern Michigan25RBJr.
2018Eastern Michigan25RBSr.5′10″207

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/playPctileMedianTotalUsageAdj. rush
2016Eastern Michigan2120.0936th (n=259)0.1318.425%0.03
2017Eastern Michigan1960.0220th (n=287)0.124.323%0.02
2018Eastern Michigan76-0.0113th (n=300)0.15-1.116%0.13

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 Eastern Michigan 8 games, 361 rushing yards, 4 TD
DateOpponentResultCarYdsTDLongRecRec yds
Aug 31vs.MonmouthW 51–⁠1712440822
Sep 8atPurdueW 20–⁠19820010––
Sep 15atBuffaloL 28–⁠3572401117
Sep 22atSan Diego StateL 20–⁠2371805––
Nov 3vs.Central MichiganW 17–⁠771706113
Nov 10vs.AkronW 27–⁠71596127––
Nov 23atKent StateW 28–⁠20171183451−1
Dec 15 ✦vs.Georgia SouthernL 21–⁠2372408––
2017 Eastern Michigan 12 games, 805 rushing yards, 8 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 1vs.CharlotteW 24–⁠7737215––
Sep 9atRutgersW 16–⁠133805––
Sep 23vs.OhioL 20–⁠27331215
Sep 30atKentuckyL 20–⁠24184019456
Oct 7atToledoL 15–⁠2095402149
Oct 14atArmyL 27–⁠2820107023––
Oct 21vs.Western MichiganL 17–⁠2024930251−3
Oct 26atNorthern IllinoisL 27–⁠30188102520
Nov 2vs.Ball StateW 56–⁠142111411910
Nov 8atCentral MichiganL 30–⁠42145201016
Nov 15atMiami (OH)W 27–⁠2418112071246
Nov 21vs.Bowling GreenW 34–⁠3124104317––
2016 Eastern Michigan 11 games, 771 rushing yards, 9 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 2vs.Mississippi Valley StateW 61–⁠141297231––
Sep 10atMissouriL 21–⁠612390130232
Sep 17atCharlotteW 37–⁠1991916238
Sep 23vs.WyomingW 27–⁠2427120127––
Oct 1atBowling GreenW 28–⁠252061011––
Oct 8vs.ToledoL 20–⁠3571708––
Oct 15atOhioW 27–⁠20122406434
Oct 29vs.Miami (OH)L 15–⁠28103306420
Nov 8atBall StateW 48–⁠4125109225571
Nov 16vs.Northern IllinoisL 24–⁠3130171229448
Dec 23 ✦vs.Old DominionL 20–⁠24930011––

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.