Running back, New Mexico, 2015–⁠17

Richard McQuarley

Number
No. 3
Height
5′11″
Weight
221 lb
Hometown
Meridian, MS

Richard McQuarley played running back at New Mexico (2015–⁠17).

At a glance

Best season
656
Rushing yards, 2016 (New Mexico, 9–⁠4)
Best game
179 yards
Vs. Air Force, week 5, 2017: No. 2 rushing game in FBS that week
National rank
No. 9
In FBS in rushing touchdowns, 2016

Career highs

179rushing yards, career highvs. Air Force, 20175rushing touchdowns, career highvs. Air Force, 2017

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2015New Mexico522304.4744
2016New Mexico1436564.61853
2017New Mexico924735.1665
Career2871,3594.73165

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHtWt
2015New Mexico3RB
2016New Mexico3RB
2017New Mexico3RB5′11″221

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
2015New Mexico540.55––29.97%0.38
2016New Mexico1520.3190th (n=259)0.1346.517%0.29
2017New Mexico96-0.084th (n=287)0.12-7.414%-0.12

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

2017 New Mexico 10 games, 473 rushing yards, 6 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 2vs.Abilene ChristianW 38–⁠1410220913
Sep 9vs.New Mexico StateL 28–⁠301030091−4
Sep 14atBoise StateL 14–⁠28103608––
Sep 23atTulsaW 16–⁠13103401816
Sep 30vs.Air ForceW 56–⁠3811179565––
Oct 14atFresno StateL 0–⁠3852009––
Oct 20vs.Colorado StateL 24–⁠271173122––
Oct 28atWyomingL 3–⁠421343010––
Nov 4vs.Utah StateL 10–⁠2493709––
Nov 11atTexas A&ML 14–⁠553−102––
2016 New Mexico 13 games, 656 rushing yards, 18 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 1vs.South DakotaW 48–⁠211355214––
Sep 10atNew Mexico StateL 31–⁠3251215––
Sep 17atRutgersL 28–⁠37652122––
Oct 1vs.San José StateW 48–⁠411683319––
Oct 7vs.Boise StateL 21–⁠49740013––
Oct 15vs.Air ForceW 45–⁠40143125––
Oct 22vs.UL MonroeW 59–⁠17968113––
Oct 29atHawai’iW 28–⁠216171916
Nov 5vs.NevadaW 35–⁠2614431815
Nov 12atUtah StateW 24–⁠21144408––
Nov 19atColorado StateL 31–⁠4972217––
Nov 26vs.WyomingW 56–⁠3515121353258
Dec 17 ✦vs.UTSAW 23–⁠201768217125
2015 New Mexico 12 games, 230 rushing yards, 7 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 5vs.Mississippi Valley StateW 66–⁠0115307––
Sep 12vs.TulsaL 21–⁠401202––
Sep 18atArizona StateL 10–⁠343302––
Sep 26atWyomingW 38–⁠28555243––
Oct 3vs.New Mexico StateW 38–⁠2941416––
Oct 10atNevadaL 17–⁠354702––
Oct 17vs.Hawai’iW 28–⁠271202––
Nov 7vs.Utah StateW 14–⁠132916––
Nov 14atBoise StateW 31–⁠242211––
Nov 21vs.Colorado StateL 21–⁠284502––
Nov 28vs.Air ForceW 47–⁠35755244––
Dec 19 ✦vs.ArizonaL 37–⁠4582304––

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.