Running back, UTEP, 2017–⁠20

Joshua Fields

Number
No. 21
Height
5′9″
Weight
195 lb
Class (2020)
Senior
Hometown
El Paso, TX

Joshua Fields played running back at UTEP (2017–⁠20).

Career highs

137rushing yards, career highvs. Louisiana Tech, 2017

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2017UTEP883594.1227
2018UTEP31571.8013
2019UTEP593125.3030
2020UTEP662093.2115
Career2449373.8330

Receiving

SeasonTeamRecYdsAvgTDLong
2017UTEP6264.3018
2018UTEP3155.0022
2019UTEP571.409
2020UTEP2126.0011
Career16603.8022

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2017UTEP21RBFr.
2018UTEP21RBSo.
2019UTEP21RBJr.
2020UTEP21RBSr.5′9″195

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
2017UTEP96-0.121st (n=287)0.12-11.715%-0.04
2018UTEP33-0.29––-9.56%–
2019UTEP66-0.084th (n=287)0.13-5.19%0.01
2020UTEP70-0.221st (n=212)0.14-15.514%-0.10

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

2020 UTEP 7 games, 209 rushing yards, 1 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 5vs.Stephen F. AustinW 24–⁠1492309111
Sep 12atTexasL 3–⁠594001––
Sep 19vs.Abilene ChristianW 17–⁠13177511511
Sep 26atUL MonroeW 31–⁠61553010––
Oct 10atLouisiana TechL 17–⁠211133011––
Oct 24atCharlotteL 28–⁠3861504––
Dec 11vs.North TexasL 43–⁠4541004––
2019 UTEP 11 games, 312 rushing yards
DateOpponentResultCarYdsTDLongRecRec yds
Aug 31vs.Houston ChristianW 36–⁠3476102616
Sep 7atTexas TechL 3–⁠38142708––
Sep 21vs.NevadaL 21–⁠371044091−5
Sep 28atSouthern MissL 13–⁠3136032−3
Oct 5vs.UTSAL 16–⁠26425021––
Oct 26vs.Louisiana TechL 21–⁠42752030––
Nov 2atNorth TexasL 26–⁠52228025––
Nov 9vs.CharlotteL 21–⁠28320022––
Nov 16atUABL 10–⁠37390419
Nov 23atNew Mexico StateL 35–⁠44433019––
Nov 30vs.RiceL 16–⁠302705––
2018 UTEP 9 games, 57 rushing yards
DateOpponentResultCarYdsTDLongRecRec yds
Sep 1vs.Northern ArizonaL 10–⁠302907––
Sep 8atUNLVL 24–⁠52––––2−7
Sep 15atTennesseeL 0–⁠244−103––
Sep 22vs.New Mexico StateL 20–⁠272705––
Sep 29atUTSAL 21–⁠304504––
Oct 20atLouisiana TechL 24–⁠3181308122
Oct 27vs.UABL 0–⁠194−502––
Nov 3atRiceW 34–⁠26215013––
Nov 10vs.Middle TennesseeL 32–⁠4851408––
2017 UTEP 11 games, 359 rushing yards, 2 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 2atOklahomaL 7–⁠5640011−1
Sep 9vs.RiceL 14–⁠311303118
Sep 15vs.ArizonaL 16–⁠63––––25
Sep 23atNew Mexico StateL 14–⁠411202––
Oct 7vs.Western KentuckyL 14–⁠154707––
Oct 14atSouthern MissL 0–⁠2461307––
Oct 28vs.UTSAL 14–⁠311141117––
Nov 4atMiddle TennesseeL 3–⁠30178702713
Nov 11atNorth TexasL 10–⁠45164501111
Nov 18vs.Louisiana TechL 21–⁠4223137126––
Nov 25atUABL 7–⁠28524010––

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.