Running back, Kansas, 2009–⁠12

Toben Opurum

Number
No. 35
Height
6′1″
Hometown
Richardson, TX
Born
Nov 18, 1990, in Richardson, Texas

Toben Opurum played running back at Kansas (2009–⁠12).

Career highs

109rushing yards, career highvs. Southern Miss, 20092rushing touchdowns, career hightwice; last vs. Duke, 2009

Rushing

SeasonTeamCarYdsAvgTDLong
2009Kansas1335544.2926

Receiving

SeasonTeamRecYdsAvgTDLong
2009Kansas131058.1130
2012Kansas11212.0012
Career141178.4130

Season lines from CollegeFootballData, regular season and bowls.

Defense before 2016

SeasonGSoloAstTklTFLSacksPBUFFHur
201078132131311
20111227184510.54117
20121124194361.5322
On file595010919.56.57410

Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources: cfbstats.com (Open Data Commons Attribution License), its game lines summed (G: the games he has a line in). A dash: the source has no number for it.

On the roster

SeasonTeamNo.PosHt
2009Kansas35RB
2010Kansas35RB
2011Kansas35RB
2012Kansas35RB6′1″

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.

Game by game

2012 Kansas 1 game, 1 catch, 12 yards
DateOpponentResultCarYdsTDLongRecRec yds
Oct 6atKansas StateL 16–⁠56––––112
2009 Kansas 11 games, 554 rushing yards, 9 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 5vs.Northern ColoradoW 49–⁠387922615
Sep 12atUTEPW 34–⁠7166211629
Sep 19vs.DukeW 44–⁠161770215350
Sep 26vs.Southern MissW 35–⁠2828109111221
Oct 10vs.Iowa StateW 41–⁠362498112217
Oct 17atColoradoL 30–⁠342312––
Oct 24vs.OklahomaL 13–⁠351359014––
Oct 31atTexas TechL 21–⁠426111928
Nov 7atKansas StateL 10–⁠172704––
Nov 14vs.NebraskaL 17–⁠311543061−5
Nov 21atTexasL 20–⁠51213012––

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.