
Receiver, Texas Tech (from Iowa), 2013–17
Derrick Willies
Lettered 2016–17 (school media guide)
- Number
- No. 11
- Height
- 6′4″
- Weight
- 210 lb
- Hometown
- San Bernadino, CA
- Born
- Oct 17, 1994, in Banning, California
Wikipedia readers: about 126 a month over the past year
Derrick Willies played receiver at Iowa (2013–14) and Texas Tech (2016–17).
Career highs
126receiving yards, career highvs. Eastern Washington, 2017Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2014 | Iowa | 4 | 71 | 17.8 | 1 | 46 |
| 2016 | Texas Tech | 18 | 288 | 16.0 | 2 | 59 |
| 2017 | Texas Tech | 18 | 304 | 16.9 | 3 | 75 |
| Career | 40 | 663 | 16.6 | 6 | 75 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Ht | Wt |
|---|---|---|---|---|---|
| 2013 | Iowa | 11 | WR | ||
| 2014 | Iowa | 11 | WR | ||
| 2016 | Texas Tech | 11 | WR | ||
| 2017 | Texas Tech | 11 | WR | 6′4″ | 210 |
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 |
|---|---|---|---|---|---|---|---|
| 2014 | Iowa | 7 | 0.89 | – | – | 6.2 | – |
| 2016 | Texas Tech | 31 | 0.34 | 20th (n=489) | 0.52 | 10.5 | 5% |
| 2017 | Texas Tech | 25 | 0.89 | – | – | 22.3 | 5% |
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
2017 Texas Tech 6 games, 18 catches, 304 yards, 3 TD
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Sep 2 | vs. | W 56–10 | 4 | 126 | 1 | 75 | 0 |
| Sep 16 | vs. | W 52–45 | 4 | 56 | 1 | 28 | – |
| Sep 23 | at | W 27–24 | 4 | 41 | 0 | 13 | – |
| Sep 30 | vs. | L 34–41 | 3 | 30 | 0 | 14 | – |
| Oct 7 | at | W 65–19 | 1 | 32 | 1 | 32 | – |
| Oct 21 | vs. | L 13–31 | 2 | 19 | 0 | 13 | – |
2016 Texas Tech 8 games, 18 catches, 288 yards, 2 TD
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Sep 3 | vs. | W 69–17 | 2 | 47 | 0 | 33 | – |
| Sep 10 | at | L 55–68 | 1 | 59 | 1 | 59 | – |
| Sep 17 | vs. | W 59–45 | 3 | 38 | 0 | 19 | – |
| Sep 29 | vs. | W 55–19 | 1 | 6 | 1 | 6 | – |
| Oct 8 | at | L 38–44 | 2 | 18 | 0 | 11 | – |
| Nov 5 | vs. | L 37–45 | 3 | 63 | 0 | 31 | – |
| Nov 12 | at | L 44–45 | 4 | 50 | 0 | 16 | – |
| Nov 19 | at | L 10–66 | 2 | 7 | 0 | 4 | – |
2014 Iowa 3 games, 4 catches, 71 yards, 1 TD
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Aug 30 | vs. | W 31–23 | 1 | 46 | 0 | 46 | – |
| Sep 6 | vs. | W 17–13 | 2 | 19 | 1 | 12 | – |
| Sep 27 | at | W 24–10 | 1 | 6 | 0 | 6 | – |
Box scores from CollegeFootballData, 2004 on. ✦ postseason; ★ a career high on file.
Other pro football
| Years | League | Team |
|---|---|---|
| 2022 | USFL | Tampa Bay Bandits |
Leagues other than the NFL, from the infobox of his Wikipedia article (CC BY-SA), as it names the teams.
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.