Running back, Kent State, 2016–⁠19

Will Matthews

Number
No. 2
Height
5′7″
Weight
201 lb
Class (2019)
Senior
Hometown
Destrehan, LA

Will Matthews played running back at Kent State (2016–⁠19).

Career highs

126rushing yards, career highat Akron, 2019

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2016Kent State311384.5051
2017Kent State541883.5125
2018Kent State291154.0121
2019Kent State1235704.6334
Career2371,0114.3551

Receiving

SeasonTeamRecYdsAvgTDLong
2016Kent State39130.3048
2017Kent State57114.2036
2018Kent State5479.4019
2019Kent State77010.0028
Career2027913.9048

Defense

SeasonTeamTklSoloTFLSacksPDHur
2017Kent State110000
2018Kent State440000
Career550000

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2016Kent State2RBFr.
2017Kent State2RBSo.
2018Kent State2RBJr.
2019Kent State2RBSr.5′7″201

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
2016Kent State280.11––3.18%–
2017Kent State–0.00––0.0–0.02
2018Kent State340.10––3.37%–
2019Kent State1310.0936th (n=287)0.1311.222%0.03

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 Kent State 8 games, 570 rushing yards, 3 TD
DateOpponentResultCarYdsTDLongRecRec yds
Oct 12atAkronW 26–⁠325126116––
Oct 19atOhioL 38–⁠451485125112
Oct 26vs.Miami (OH)L 16–⁠231552010210
Nov 5atToledoL 33–⁠351355025128
Nov 14vs.BuffaloW 30–⁠271137015––
Nov 23vs.Ball StateW 41–⁠381485034––
Nov 29atEastern MichiganW 34–⁠2614740111−4
Dec 20 ✦vs.Utah StateW 51–⁠411756112224
2018 Kent State 8 games, 115 rushing yards, 1 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 1atIllinoisL 24–⁠318603326
Sep 8vs.HowardW 54–⁠14646116––
Sep 15atPenn StateL 10–⁠6341605––
Sep 22atOle MissL 17–⁠381−300––
Sep 29atBall StateL 24–⁠52849021221
Oct 6vs.OhioL 26–⁠27––––––
Oct 30atBowling GreenW 35–⁠282101––
Nov 15vs.ToledoL 34–⁠56––––––
2017 Kent State 9 games, 188 rushing yards, 1 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 2atClemsonL 3–⁠566803––
Sep 9vs.HowardW 38–⁠311064021––
Sep 16atMarshallL 0–⁠212302––
Sep 23atLouisvilleL 3–⁠42616013––
Sep 30vs.BuffaloL 13–⁠276190912
Oct 7atNorthern IllinoisL 3–⁠2481506––
Oct 14vs.Miami (OH)W 17–⁠1482609––
Oct 21atOhioL 3–⁠4841309136
Oct 31vs.Bowling GreenL 16–⁠44424125333
2016 Kent State 8 games, 138 rushing yards
DateOpponentResultCarYdsTDLongRecRec yds
Sep 3atPenn StateL 13–⁠332603––
Sep 10vs.North Carolina A&TL 36–⁠392908––
Sep 17vs.MonmouthW 27–⁠74503––
Sep 24atAlabamaL 0–⁠483302243
Oct 8atBuffaloW 44–⁠20562051––
Oct 15atMiami (OH)L 14–⁠181147017148
Oct 29atCentral MichiganW 27–⁠241404––
Nov 25vs.Northern IllinoisL 21–⁠313203––

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.