Running back, Utah (from Washington State), 2024–26
Wayshawn Parker
- Number
- No. 1
- Height
- 5′10″
- Weight
- 205 lb
- Class (2026)
- Junior
- Hometown
- Richmond, CA
Wayshawn Parker plays running back for Utah, after Washington State (2024). Last time out, at Colorado: 23 carries, 98 yards; 2 catches, 11 yards. Parker leads Utah in rushing touchdowns and rushing yards this season.
2026 so far
597 rushing yards, 7 TD
Last game: 23 carries, 98 yards; 2 catches, 11 yards at Colorado, W 27–24
Next game: vs. Houston, Oct 24
Filled bars: wins; outlined: losses.
Career highs
174rushing yards, career highat Iowa State, 20262rushing touchdowns, career highfour times; last vs. Kansas, 20262receiving touchdowns, career highvs. Idaho, 2026Rushing
* The season in progress, so far.
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2024 | Washington State | 137 | 735 | 5.4 | 4 | 75 |
| 2025 | Utah | 149 | 981 | 6.6 | 6 | 64 |
| 2026 | Utah | 89 | 597 | 6.7 | 7 | 90 |
| Career | 375 | 2,313 | 6.2 | 17 | 90 | |
Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2024 | Washington State | 10 | 100 | 10.0 | 1 | 52 |
| 2025 | Utah | 13 | 185 | 14.2 | 3 | 52 |
| 2026 | Utah | 19 | 201 | 10.6 | 4 | 36 |
| Career | 42 | 486 | 11.6 | 8 | 52 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2024 | Washington State | 1 | RB | Fr. | ||
| 2025 | Utah | 1 | RB | So. | ||
| 2026 | Utah | 1 | RB | Jr. | 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
| Season | Team | Plays | EPA/play | Pctile | Median | Total | Usage | Adj. rush |
|---|---|---|---|---|---|---|---|---|
| 2024 | Washington State | 130 | 0.00 | 12th (n=434) | 0.16 | 0.5 | 19% | 0.04 |
| 2025 | Utah | 161 | 0.28 | 94th (n=576) | 0.10 | 45.3 | 17% | 0.18 |
| 2026 | Utah | 109 | 0.48 | 99th (n=478) | 0.10 | 52.1 | 25% | 0.42 |
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
| Season | Team | Success | Line yards | Second level | Open field | Stuffed |
|---|---|---|---|---|---|---|
| 2025 | Utah | 44% | 3.40 | 1.20 | 2.00 | 14% |
| 2026 | Utah | 54% | 3.40 | 1.30 | 2.50 | 19% |
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 Utah 6 games, 597 rushing yards, 7 TD
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 3 | vs. | W 66–14 | 12 | 71 | 1 | 21 | 3 | 23 |
| Sep 12 | vs. | W 43–10 | 10 | 53 | 2 | 15 | 5 | 65 |
| Sep 19 | vs. | W 33–0 | 10 | 30 | 0 | 14 | 2 | 1 |
| Sep 26 | at | W 31–17 | 18 | 174 | 2 | 54 | 5 | 65 |
| Oct 10 | vs. | W 41–24 | 16 | 171 | 2 | 90 | 2 | 36 |
| Oct 17 | at | W 27–24 | 23 | 98 | 0 | 14 | 2 | 11 |
2025 Utah 13 games, 981 rushing yards, 6 TD
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Aug 30 | at | W 43–10 | 11 | 62 | 1 | 13 | – | – |
| Sep 6 | vs. | W 63–9 | 6 | 50 | 1 | 43 | 1 | 52 |
| Sep 13 | at | W 31–6 | 10 | 80 | 0 | 20 | 2 | 9 |
| Sep 20 | vs. | L 10–34 | 6 | 22 | 1 | 5 | 1 | 9 |
| Sep 27 | at | W 48–14 | 9 | 66 | 0 | 40 | 2 | 21 |
| Oct 11 | vs. | W 42–10 | 10 | 55 | 0 | 19 | – | – |
| Oct 18 | at | L 21–24 | 8 | 23 | 0 | 9 | 1 | −1 |
| Oct 25 | vs. | W 53–7 | 10 | 145 | 1 | 58 | – | – |
| Nov 1 | vs. | W 45–14 | 17 | 104 | 1 | 39 | – | – |
| Nov 15 | at | W 55–28 | 15 | 129 | 1 | 64 | 1 | 5 |
| Nov 22 | vs. | W 51–47 | 19 | 100 | 0 | 25 | 1 | 5 |
| Nov 28 | at | W 31–21 | 12 | 95 | 0 | 34 | 1 | 32 |
| Dec 31 ✦ | vs. | W 44–22 | 16 | 50 | 0 | 16 | 3 | 53 |
2024 Washington State 12 games, 735 rushing yards, 4 TD
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Aug 31 | vs. | W 70–30 | 8 | 96 | 1 | 54 | 1 | 52 |
| Sep 7 | vs. | W 37–16 | 11 | 69 | 1 | 43 | 1 | 2 |
| Sep 14 | vs. | W 24–19 | 10 | 49 | 0 | 37 | 1 | 16 |
| Sep 20 | vs. | W 54–52 | 22 | 76 | 0 | 20 | 1 | 1 |
| Sep 28 | at | L 24–45 | 11 | 35 | 0 | 21 | – | – |
| Oct 12 | at | W 25–17 | 12 | 63 | 0 | 22 | 1 | −2 |
| Oct 19 | vs. | W 42–10 | 9 | 25 | 0 | 9 | – | – |
| Oct 26 | at | W 29–26 | 9 | 33 | 0 | 10 | – | – |
| Nov 9 | vs. | W 49–28 | 11 | 149 | 2 | 75 | 1 | 10 |
| Nov 16 | at | L 35–38 | 11 | 47 | 0 | 12 | 2 | 9 |
| Nov 23 | at | L 38–41 | 9 | 48 | 0 | 11 | 0 | −3 |
| Nov 30 | vs. | L 14–15 | 14 | 45 | 0 | 13 | 2 | 15 |
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.
