Running back, UCLA, 2015–⁠18

Soso Jamabo

Number
No. 1
Height
6′2″
Weight
212 lb
Class (2018)
Senior
Hometown
Plano, TX

Soso Jamabo played running back at UCLA (2015–⁠18).

Career highs

100rushing yards, career highat Stanford, 20173rushing touchdowns, career highvs. UNLV, 201685receiving yards, career highat Arizona State, 2016

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2015UCLA664036.1439
2016UCLA823213.9331
2017UCLA904465.0649
2018UCLA5122.405
Career2431,1824.91349

Receiving

SeasonTeamRecYdsAvgTDLong
2015UCLA55811.6036
2016UCLA1619712.3066
2017UCLA1720412.0032
Career3845912.1066

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2015UCLA1RBFr.
2016UCLA1RBSo.
2017UCLA1RBJr.
2018UCLA1RBSr.6′2″212

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
2015UCLA750.2382nd (n=268)0.1217.28%0.15
2016UCLA1070.1039th (n=259)0.1310.514%0.03
2017UCLA1130.1867th (n=287)0.1220.215%0.11
2018UCLA5-0.22––-1.1––

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 UCLA 2 games, 12 rushing yards
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 15vs.Fresno StateL 14–⁠384120–––
Sep 28atColoradoL 16–⁠38100–––
2017 UCLA 10 games, 446 rushing yards, 6 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 3vs.Texas A&MW 45–⁠4474611100
Sep 23atStanfordL 34–⁠581210013410
Sep 30vs.ColoradoW 27–⁠23217012110
Oct 14atArizonaL 30–⁠4783314530
Oct 21vs.OregonW 31–⁠1415661180
Oct 28atWashingtonL 23–⁠449280–––
Nov 11vs.Arizona StateW 44–⁠3731911−40
Nov 18atUSCL 23–⁠2896202410
Nov 24vs.CaliforniaW 30–⁠2742302380
Dec 26 ✦vs.Kansas StateL 17–⁠352−10160
2016 UCLA 11 games, 321 rushing yards, 3 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 3atTexas A&ML 24–⁠31239105410
Sep 10vs.UNLVW 42–⁠21119031220
Sep 24vs.StanfordL 13–⁠227170140
Oct 1vs.ArizonaW 45–⁠246−1201330
Oct 8atArizona StateL 20–⁠233904850
Oct 15atWashington StateL 21–⁠272120–––
Oct 22vs.UtahL 45–⁠521−10150
Nov 3atColoradoL 10–⁠2023660260
Nov 12vs.Oregon StateW 38–⁠243360110
Nov 19vs.USCL 14–⁠36250–––
Nov 26atCaliforniaL 10–⁠36180–––
2015 UCLA 13 games, 403 rushing yards, 4 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 5vs.VirginiaW 34–⁠169790–––
Sep 12atUNLVW 37–⁠3490–––
Sep 19vs.BYUW 24–⁠232−10120
Sep 26atArizonaW 56–⁠309961–––
Oct 3vs.Arizona StateL 23–⁠381−20–––
Oct 15atStanfordL 35–⁠564170–––
Oct 22vs.CaliforniaW 40–⁠24187912180
Oct 31vs.ColoradoW 35–⁠314201–––
Nov 7atOregon StateW 41–⁠09901–––
Nov 14vs.Washington StateL 27–⁠311120120
Nov 21atUtahW 17–⁠9430–––
Nov 28atUSCL 21–⁠40110–––
Dec 26 ✦vs.NebraskaL 29–⁠37–––1360

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.