Running back, Arizona, 2011–⁠15

Jared Baker

Lettered 2012–⁠15 (school media guide)

Number
No. 23
Height
5′8″
Hometown
Los Angeles, CA

Jared Baker played running back at Arizona (2011–⁠15).

Career highs

207rushing yards, career highat Colorado, 20153rushing touchdowns, career hightwice; last vs. New Mexico, 2015

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2012Arizona20854.3116
2013Arizona271274.7037
2014Arizona25994.0217
2015Arizona1317986.1979
Career2031,1095.51279

Returns

SeasonTeamKRYdsTD
2012Arizona51000
2013Arizona92100
2014Arizona2290
2015Arizona2510
Career183900

Receiving

SeasonTeamRecYdsAvgTDLong
2013Arizona11717.0017
2014Arizona45012.5141
2015Arizona111019.2125
Career1616810.5241

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHt
2011Arizona23RB
2012Arizona23RB
2013Arizona23RB
2014Arizona23RB
2015Arizona23RB5′8″

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
2013Arizona280.05––1.310%–
2014Arizona290.26––7.67%–
2015Arizona1480.1663rd (n=268)0.1223.516%0.26

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

2015 Arizona 12 games, 798 rushing yards, 9 TD
DateOpponentResultCarRush ydsRush TDKRYds
Sep 3vs.UTSAW 42–⁠329350118
Sep 12atNevadaW 44–⁠20350––
Sep 19vs.Northern ArizonaW 77–⁠135420133
Sep 26vs.UCLAL 30–⁠5610581––
Oct 10vs.Oregon StateW 44–⁠7101230––
Oct 17atColoradoW 38–⁠31232072––
Oct 24vs.Washington StateL 42–⁠4511223––
Oct 31atWashingtonL 3–⁠4919670––
Nov 7atUSCL 30–⁠3813630––
Nov 14vs.UtahW 37–⁠3013670––
Nov 21atArizona StateL 37–⁠52320––
Dec 19 ✦vs.New MexicoW 45–⁠37121073––
2014 Arizona 6 games, 99 rushing yards, 2 TD
DateOpponentResultCarRush ydsRush TDKRYds
Aug 29vs.UNLVW 58–⁠136210––
Sep 4atUTSAW 26–⁠234320––
Sep 13vs.NevadaW 35–⁠28100114
Oct 11vs.USCL 26–⁠2812432––
Oct 25atWashington StateW 59–⁠37–––115
Nov 22atUtahW 42–⁠10230––
2013 Arizona 9 games, 127 rushing yards
DateOpponentResultCarRush ydsRush TDKRYds
Aug 30vs.Northern ArizonaW 35–⁠07290––
Sep 7atUNLVW 58–⁠1312660––
Sep 14vs.UTSAW 38–⁠135250––
Oct 19vs.UtahW 35–⁠24–––235
Oct 26atColoradoW 44–⁠20370––
Nov 2atCaliforniaW 33–⁠28–––255
Nov 9vs.UCLAL 26–⁠31–––122
Nov 16vs.Washington StateL 17–⁠24–––259
Nov 30atArizona StateL 21–⁠58–––239
2012 Arizona 7 games, 85 rushing yards, 1 TD
DateOpponentResultCarRush ydsRush TDKRYds
Sep 15vs.South Carolina StateW 56–⁠010441––
Oct 20vs.WashingtonW 52–⁠174280––
Nov 3atUCLAL 10–⁠66480––
Nov 10vs.ColoradoW 56–⁠31250241
Nov 17atUtahW 34–⁠24–––118
Nov 23vs.Arizona StateL 34–⁠41–––113
Dec 15 ✦vs.NevadaW 49–⁠48–––128

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.