Running back, California (from Purdue), 2019–⁠23

King Doerue

Number
No. 23
Height
5′10″
Weight
205 lb
Class (2023)
Junior
Hometown
Amarillo, TX

King Doerue played running back at Purdue (2019–⁠22) and California (2023).

Career highs

95rushing yards, career highvs. Minnesota, 20212rushing touchdowns, career hightwice; last vs. Penn State, 20226catches, career hightwice; last vs. Minnesota, 2021

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2019Purdue1304513.5526
2020Purdue16674.2016
2021Purdue1355333.9231
2022Purdue27973.639
Career3081,1483.71031

Receiving

SeasonTeamRecYdsAvgTDLong
2019Purdue201487.4222
2020Purdue12020.0120
2021Purdue201567.8046
2022Purdue6579.5032
Career473818.1346

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2019Purdue23RBYr 1
2020Purdue23RBYr 2
2021Purdue23RBYr 3
2022Purdue23RBYr 4
2023California23RBJr. (Yr 5)5′10″205

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
2019Purdue166-0.0110th (n=287)0.13-2.018%0.05
2020Purdue190.03––0.5––
2021Purdue–0.00––-0.1–0.06
2022Purdue330.18––5.810%–

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

2022 Purdue 4 games, 97 rushing yards, 3 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 1vs.Penn StateL 31–⁠35155722100
Sep 10vs.Indiana StateW 56–⁠0371170
Oct 15vs.NebraskaW 43–⁠3783102380
Oct 22atWisconsinL 24–⁠35120120
2021 Purdue 12 games, 533 rushing yards, 2 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 4vs.Oregon StateW 30–⁠21570–––
Sep 11atUConnW 49–⁠012741–––
Sep 18atNotre DameL 13–⁠27104506390
Oct 2vs.MinnesotaL 13–⁠20219506390
Oct 16atIowaW 24–⁠718480130
Oct 23vs.WisconsinL 13–⁠309200–––
Oct 30atNebraskaW 28–⁠23177401−40
Nov 6vs.Michigan StateW 40–⁠29133213600
Nov 13atOhio StateL 31–⁠59102602110
Nov 20vs.NorthwesternW 32–⁠146180–––
Nov 27vs.IndianaW 44–⁠74490180
Dec 30 ✦vs.TennesseeW 48–⁠4510450–––
2020 Purdue 4 games, 67 rushing yards
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Nov 14vs.NorthwesternL 20–⁠27100–––
Nov 20atMinnesotaL 31–⁠347150–––
Nov 28vs.RutgersL 30–⁠376470–––
Dec 5vs.NebraskaL 27–⁠372501201
2019 Purdue 12 games, 451 rushing yards, 5 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Aug 30atNevadaL 31–⁠34110–––
Sep 7vs.VanderbiltW 42–⁠24590–––
Sep 14vs.TCUL 13–⁠3411270190
Sep 28vs.MinnesotaL 31–⁠38209424321
Oct 5atPenn StateL 7–⁠3511260–––
Oct 12vs.MarylandW 40–⁠14196913280
Oct 19atIowaL 20–⁠26102603160
Oct 26vs.IllinoisL 6–⁠2415370–––
Nov 2vs.NebraskaW 31–⁠27157115311
Nov 9atNorthwesternW 24–⁠2294313100
Nov 23atWisconsinL 24–⁠459260–––
Nov 30vs.IndianaL 41–⁠4452201220

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.