Running back, Arizona (from Portland State), 2022–⁠26

Quincy Craig

Lettered 2025 (school media guide)

Number
No. 24
Height
5′10″
Weight
200 lb
Class (2026)
Senior
Hometown
Garden Grove, CA

Quincy Craig plays running back for Arizona, after Portland State (2022–⁠24). Last time out, at West Virginia: 2 carries, 44 yards, 1 TD; 1 catch, −2 yards.

2026 so far

186 rushing yards, 1 TD

Last game: 2 carries, 44 yards, 1 TD; 1 catch, −2 yards at West Virginia, W 52–⁠31

Next game: vs. Iowa State, Oct 24

Game by game this season, rushing yards
  1. 24NAU
  2. 6@BYU
  3. 23NIU
  4. 12@WSU
  5. 77CIN
  6. 44@WVU

Filled bars: wins; outlined: losses.

Career highs

137rushing yards, career highvs. Northern Colorado, 20242rushing touchdowns, career hightwice; last vs. Northern Colorado, 20246catches, career highat Wyoming, 20232receiving touchdowns, career hightwice; last vs. UC Davis, 2024

Rushing

Rushing yards, season by season, with his team’s record

* The season in progress, so far.

SeasonTeamCarYdsAvgTDLong
2022Portland State382215.8236
2023Portland State664106.2367
2024Portland State1156025.2537
2025Arizona653645.6254
2026Arizona241867.8140
Career3081,7835.81367

Receiving

SeasonTeamRecYdsAvgTDLong
2022Portland State294.507
2023Portland State1920710.9332
2024Portland State333059.2543
2025Arizona141148.1124
2026Arizona8526.5011
Career766879.0943

Returns

SeasonTeamKRYdsTDPRYdsTD
2022Portland State1250–––
2023Portland State15705520
2024Portland State91860120
2025Arizona2430–––
2026Arizona100–––
Career1431106540

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
2022Portland State24RBYr 1
2023Portland State24RBYr 2
2024Portland State24RBYr 3
2025Arizona24RBYr 4
2026Arizona24RBSr. (Yr 5)5′10″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
2022Portland State (FCS)220.25––5.511%–
2023Portland State (FCS)860.4396th (n=450)0.1736.922%–
2024Portland State (FCS)1450.3289th (n=434)0.1647.020%–
2025Arizona880.1463rd (n=576)0.1012.510%0.17
2026Arizona320.32––10.38%–

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.

Rushing detail

SeasonTeamSuccessLine yardsSecond levelOpen fieldStuffed
2025Arizona39%3.101.101.5020%
2026Arizona48%4.001.702.909%

Where his yards came from, per carry: line yards are the ones credited to the blockers (the first few, and losses), second level the yards 5 to 10 past the line, open field those beyond 10. Success: carries that kept the offense on schedule. Stuffed: carries stopped at or behind the line. From CollegeFootballData, FBS games, 2025 on.

Game by game

2026 Arizona 6 games, 186 rushing yards, 1 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 5vs.Northern ArizonaW 35–⁠752402190
Sep 12atBYUL 17–⁠283603220
Sep 19vs.Northern IllinoisW 42–⁠173230150
Sep 26atWashington StateW 34–⁠244120180
Oct 3vs.CincinnatiW 34–⁠77770–––
Oct 10atWest VirginiaW 52–⁠3124411−20
2025 Arizona 12 games, 364 rushing yards, 2 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Aug 30vs.Hawai’iW 40–⁠671251–––
Sep 6vs.Weber StateW 48–⁠38310160
Sep 12vs.Kansas StateW 23–⁠17390–––
Sep 27atIowa StateL 14–⁠39460160
Oct 4vs.Oklahoma StateW 41–⁠13–––3240
Oct 11vs.BYUL 27–⁠3363602110
Oct 18atHoustonL 28–⁠31220–––
Nov 1atColoradoW 52–⁠1772501100
Nov 8vs.KansasW 24–⁠2034712131
Nov 15atCincinnatiW 30–⁠24115202160
Nov 28atArizona StateW 23–⁠74202280
Jan 2 ✦vs.SMUL 19–⁠2410290–––
2024 Portland State 11 games, 602 rushing yards, 5 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Aug 31atWashington StateL 30–⁠70105404240
Sep 7atWeber StateL 16–⁠43147105221
Sep 21atBoise StateL 14–⁠567704200
Sep 28atChattanoogaL 30–⁠451010314241
Oct 5vs.UC DavisL 26–⁠277303572
Oct 12atIdaho StateW 42–⁠3892103190
Oct 19vs.Montana StateL 14–⁠4463404160
Nov 2atSacramento StateW 58–⁠38124212420
Nov 9vs.IdahoL 30–⁠3994001201
Nov 16atMontanaL 17–⁠28169012480
Nov 23vs.Northern ColoradoW 45–⁠131513721130

No box score in the source for Sep 14 vs. South Dakota, so that game is not listed.

2023 Portland State 6 games, 410 rushing yards, 3 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 2atOregonL 7–⁠818420–––
Sep 9atWyomingL 17–⁠31125406550
Sep 16vs.North AmericanW 91–⁠076922270
Sep 23vs.Cal PolyW 59–⁠21118213411
Sep 30atMontana StateL 22–⁠38186004490
Oct 14atNorthern ArizonaW 45–⁠211010304352
2022 Portland State 4 games, 221 rushing yards, 2 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Oct 1vs.Northern ArizonaW 35–⁠27320120
Oct 15vs.Weber StateL 7–⁠42250170
Nov 11vs.Sacramento StateL 17–⁠45151071–––
Nov 19atCal PolyL 42–⁠49181071–––

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.