Rodney Anderson, 2018
Photo: Bobak Ha’Eri, CC BY 3.0, via Wikimedia Commons

Running back, Oklahoma, 2015–⁠18

Rodney Anderson

Number
No. 24
Height
6′1″
Weight
220 lb
Class (2018)
Junior
Hometown
Katy, TX
Born
Sep 12, 1996, in Katy, Texas

Wikipedia readers: about 617 a month over the past year

Rodney Anderson played running back at Oklahoma (2015–⁠18). The Cincinnati Bengals took Anderson in round 6, No. 211 overall in the 2019 NFL Draft.

At a glance

Best season
1,161
Rushing yards, 2017 (Oklahoma, 12–⁠2)
Best game
201 yards
Vs. Georgia, bowl season 2017: No. 3 rushing game in FBS that week
Drafted
No. 211
Round 6, 2019 NFL Draft (Cincinnati Bengals)

Career highs

201rushing yards, career highvs. Georgia, 20174rushing touchdowns, career highvs. West Virginia, 2017139receiving yards, career highvs. TCU, 20172receiving touchdowns, career highvs. TCU, 2017

Honors

Team titles: Big 12 champions, 2015, 2016, 2017 and 2018

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2015Oklahoma155.005
2017Oklahoma1881,1616.21358
2018Oklahoma1111910.8365
Career2001,2856.41665

Receiving

SeasonTeamRecYdsAvgTDLong
2017Oklahoma1728116.5546

Returns

SeasonTeamKRYdsTDPRYdsTD
2017Oklahoma4380170

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2015Oklahoma24RBYr 1
2016Oklahoma24RBYr 2
2017Oklahoma24RBYr 3
2018Oklahoma24RBJr. (Yr 4)6′1″220

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
2015Oklahoma10.08––0.1––
2017Oklahoma2080.3394th (n=287)0.1268.722%0.34
2018Oklahoma120.64––7.6––

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 Oklahoma 2 games, 119 rushing yards, 3 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 1vs.Florida AtlanticW 63–⁠145100265––
Sep 8vs.UCLAW 49–⁠21619110––
2017 Oklahoma 13 games, 1,161 rushing yards, 13 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 2vs.UTEPW 56–⁠74141419
Sep 9atOhio StateW 31–⁠1631008112
Sep 16vs.TulaneW 56–⁠144805––
Oct 7vs.Iowa StateL 31–⁠38120216
Oct 14vs.TexasW 29–⁠241048121––
Oct 21atKansas StateW 42–⁠3519147136430
Oct 28vs.Texas TechW 49–⁠2724181118––
Nov 4atOklahoma StateW 62–⁠5221111121248
Nov 11vs.TCUW 38–⁠20231512305139
Nov 18atKansasW 41–⁠31677016239
Nov 25vs.West VirginiaW 59–⁠3113118458––
Dec 2vs.TCUW 41–⁠172493014––
Jan 1 ✦vs.GeorgiaL 48–⁠54262012451−2
2015 Oklahoma 1 game, 5 rushing yards
DateOpponentResultCarYdsTDLongRecRec yds
Sep 5vs.AkronW 41–⁠31505––

Box scores from CollegeFootballData, 2004 on. ✦ postseason; ★ a career high on file.

Before the draft

DrillCombine 2019
Height6′0⅜″
Weight224 lb
Arm length30¾″
Hand size9¾″
Bench press25 reps

Combine and pro day results compiled by array-carpenter (nfl-draft-data).

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.