Receiver, California (from Michigan), 2014–18
Maurice Ways
Lettered 2015–17 at Michigan (school media guide)
- Number
- No. 85
- Height
- 6′3″
- Weight
- 215 lb
- Hometown
- Beverly Hills, MI
Maurice Ways played receiver at Michigan (2014–17) and California (2018).
Career highs
8catches, career highat Arizona, 201897receiving yards, career highat Arizona, 2018Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2015 | Michigan | 3 | 40 | 13.3 | 0 | 21 |
| 2016 | Michigan | 2 | 24 | 12.0 | 0 | 22 |
| 2017 | Michigan | 3 | 7 | 2.3 | 0 | 4 |
| 2018 | California | 34 | 383 | 11.3 | 1 | 41 |
| Career | 42 | 454 | 10.8 | 1 | 41 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Ht | Wt |
|---|---|---|---|---|---|
| 2014 | Michigan | 85 | WR | ||
| 2015 | Michigan | 85 | WR | ||
| 2016 | Michigan | 85 | WR | ||
| 2017 | Michigan | 85 | WR | ||
| 2018 | California | 85 | WR | 6′3″ | 215 |
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 |
|---|---|---|---|---|---|---|---|
| 2015 | Michigan | 3 | 1.33 | – | – | 4.0 | – |
| 2016 | Michigan | 2 | 1.25 | – | – | 2.5 | – |
| 2017 | Michigan | 3 | 0.22 | – | – | 0.7 | – |
| 2018 | California | 51 | 0.45 | 35th (n=497) | 0.53 | 22.7 | 6% |
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). From CollegeFootballData, 2013 on.
Game by game
2018 California 12 games, 34 catches, 383 yards, 1 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 1 | vs. North Carolina | W 24–17 | 1 | 23 | 0 | 23 |
| Sep 15 | vs. Idaho State | W 45–23 | 3 | 22 | 0 | 8 |
| Sep 29 | vs. Oregon | L 24–42 | 2 | 18 | 0 | 13 |
| Oct 6 | at Arizona | L 17–24 | 8 | 97 | 0 | 41 |
| Oct 13 | vs. UCLA | L 7–37 | 2 | 12 | 0 | 7 |
| Oct 20 | at Oregon State | W 49–7 | 1 | 14 | 0 | 14 |
| Oct 27 | vs. Washington | W 12–10 | 2 | 25 | 0 | 16 |
| Nov 3 | at Washington State | L 13–19 | 3 | 46 | 0 | 35 |
| Nov 10 | at USC | W 15–14 | 1 | 7 | 0 | 7 |
| Nov 24 | vs. Colorado | W 33–21 | 3 | 43 | 1 | 30 |
| Dec 1 | vs. Stanford | L 13–23 | 5 | 39 | 0 | 12 |
| Dec 26 ✦ | vs. TCU | L 7–10 | 3 | 37 | 0 | 22 |
2017 Michigan 3 games, 3 catches, 7 yards
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 23 | at Purdue | W 28–10 | 1 | 4 | 0 | 4 |
| Oct 7 | vs. Michigan State | L 10–14 | 1 | 3 | 0 | 3 |
| Nov 4 | vs. Minnesota | W 33–10 | 1 | 0 | 0 | 0 |
2016 Michigan 2 games, 2 catches, 24 yards
2015 Michigan 3 games, 3 catches, 40 yards
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 19 | vs. UNLV | W 28–7 | 1 | 21 | 0 | 21 |
| Oct 10 | vs. Northwestern | W 38–0 | 1 | 10 | 0 | 10 |
| Nov 21 | at Penn State | W 28–16 | 1 | 9 | 0 | 9 |
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.