Running back, Purdue, 2016–20
Richie Worship
- Number
- No. 34
- Height
- 6′0″
- Weight
- 250 lb
- Class (2020)
- Senior
- Hometown
- Cleveland, OH
Richie Worship played running back at Purdue (2016–20).
Career highs
89rushing yards, career highvs. Nebraska, 2017Rushing
Receiving
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2016 | Purdue | 34 | RB | Yr 1 | ||
| 2017 | Purdue | 34 | RB | Yr 2 | ||
| 2018 | Purdue | 34 | RB | Yr 3 | ||
| 2019 | Purdue | 34 | RB | Yr 4 | ||
| 2020 | Purdue | 34 | RB | Sr. (Yr 5) | 6′0″ | 250 |
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 |
|---|---|---|---|---|---|---|---|---|
| 2016 | Purdue | 45 | 0.08 | – | – | 3.6 | 7% | 0.10 |
| 2017 | Purdue | 63 | 0.18 | 66th (n=287) | 0.12 | 11.1 | 10% | 0.05 |
| 2019 | Purdue | 1 | -0.20 | – | – | -0.2 | – | – |
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
2019 Purdue 1 game, 3 rushing yards
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Oct 19 | at Iowa | L 20–26 | 1 | 3 | 0 | – | – | – |
2017 Purdue 10 games, 257 rushing yards, 3 TD
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Sep 2 | vs. Louisville | L 28–35 | 1 | −4 | 0 | 1 | 8 | 1 |
| Sep 8 | vs. Ohio | W 44–21 | 3 | 16 | 0 | – | – | – |
| Sep 16 | at Missouri | W 35–3 | 6 | 13 | 1 | 1 | 1 | 1 |
| Sep 23 | vs. Michigan | L 10–28 | 2 | 18 | 0 | – | – | – |
| Oct 7 | vs. Minnesota | W 31–17 | 1 | 6 | 0 | – | – | – |
| Oct 14 | at Wisconsin | L 9–17 | 3 | 13 | 0 | – | – | – |
| Oct 21 | at Rutgers | L 12–14 | 5 | 51 | 0 | 1 | 10 | 0 |
| Oct 28 | vs. Nebraska | L 24–25 | 18 | 89 | 1 | 1 | 7 | 0 |
| Nov 4 | vs. Illinois | W 29–10 | 10 | 44 | 1 | 5 | 43 | 0 |
| Nov 11 | at Northwestern | L 13–23 | 4 | 11 | 0 | 1 | 4 | 0 |
2016 Purdue 8 games, 133 rushing yards, 2 TD
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Sep 3 | vs. Eastern Kentucky | W 45–24 | 4 | 20 | 0 | 1 | 3 | 0 |
| Sep 10 | vs. Cincinnati | L 20–38 | 1 | 4 | 1 | – | – | – |
| Sep 24 | vs. Nevada | W 24–14 | 4 | 10 | 0 | – | – | – |
| Oct 1 | at Maryland | L 7–50 | 1 | −1 | 0 | – | – | – |
| Oct 8 | atIllinois | W 34–31 | 13 | 60 | 1 | 2 | 24 | 0 |
| Oct 15 | vs.Iowa | L 35–49 | 3 | 9 | 0 | 4 | 15 | 0 |
| Oct 22 | atNebraska | L 14–27 | 3 | 8 | 0 | – | – | – |
| Oct 29 | vs. Penn State | L 24–62 | 6 | 23 | 0 | 1 | 7 | 0 |
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.