Running back, Toledo, 2016–⁠19

Ronnie Jones

Number
No. 5
Height
6′1″
Weight
200 lb
Class (2019)
Senior
Hometown
Pittsburgh, PA

Ronnie Jones played running back at Toledo (2016–⁠19).

Career highs

2rushing touchdowns, career highat Ball State, 2019

Team titles: MAC champions, 2017

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2018Toledo291445.0024
2019Toledo342336.9444
Career633776.0444

Returns

SeasonTeamKRYdsTDPRYdsTD
2016Toledo–––1271
2018Toledo81600–––
2019Toledo225540–––
Career3071401271

Defense

SeasonTeamTklSoloTFLSacksPDHur
2016Toledo430000
2017Toledo1260000
2018Toledo330000
2019Toledo200000
Career21120000

Season lines from CollegeFootballData, regular season and bowls. A dash: the source has no number for that season (often an FCS season), and career totals count only the numbers on file.

On the roster

SeasonTeamNo.PosClassHtWt
2016Toledo5RBFr.
2017Toledo5RBSo.
2018Toledo5RBJr.
2019Toledo5RBSr.6′1″200

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
2018Toledo290.12––3.35%–
2019Toledo390.59––23.25%0.30

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

2019 Toledo 11 games, 233 rushing yards, 4 TD
DateOpponentResultCarRush ydsRush TDKRYdsPR
Aug 31atKentuckyL 24–⁠382240137–
Sep 14vs.Murray StateW 45–⁠0160–––
Sep 28vs.BYUW 28–⁠21240243–
Oct 5vs.Western MichiganW 31–⁠24150250–
Oct 12atBowling GreenL 7–⁠20–––218–
Oct 19atBall StateL 14–⁠5287224106–
Oct 26vs.Eastern MichiganW 37–⁠34270377–
Nov 5vs.Kent StateW 35–⁠335630–––
Nov 13vs.Northern IllinoisL 28–⁠3111451–––
Nov 20atBuffaloL 30–⁠492713110–
Nov 29atCentral MichiganL 7–⁠49–––5113–
2018 Toledo 10 games, 144 rushing yards
DateOpponentResultCarRush ydsRush TDKRYdsPR
Sep 1vs.VMIW 66–⁠35190–––
Sep 22vs.NevadaW 63–⁠44––––––
Sep 29atFresno StateL 27–⁠496510255–
Oct 6vs.Bowling GreenW 52–⁠36–––127–
Oct 13atEastern MichiganL 26–⁠28–––114–
Oct 25atWestern MichiganW 51–⁠244100114–
Oct 31vs.Ball StateW 45–⁠135180–––
Nov 7atNorthern IllinoisL 15–⁠385250350–
Nov 15atKent StateW 56–⁠34250–––
Nov 23vs.Central MichiganW 51–⁠132160–––
2017 Toledo 8 games, 12 tackles
DateOpponentResultCarRush ydsRush TDKRYdsPR
Aug 31vs.ElonW 47–⁠13––––––
Sep 9atNevadaW 37–⁠24––––––
Sep 16vs.TulsaW 54–⁠51––––––
Oct 7vs.Eastern MichiganW 20–⁠15––––––
Oct 14atCentral MichiganW 30–⁠10––––––
Oct 26atBall StateW 58–⁠17––––––
Nov 8atOhioL 10–⁠38––––––
Nov 15atBowling GreenW 66–⁠37––––––
2016 Toledo 5 games, 4 tackles
DateOpponentResultCarRush ydsRush TDKRYdsPR
Sep 10vs.MaineW 45–⁠3–––––1
Sep 17vs.Fresno StateW 52–⁠17––––––
Oct 15vs.Bowling GreenW 42–⁠35––––––
Oct 22vs.Central MichiganW 31–⁠17––––––
Nov 2atAkronW 48–⁠17––––––

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.