Receiver, Portland State, 2014–17
Darnell Adams
- Number
- No. 7
- Height
- 6′2″
- Weight
- 200 lb
- Hometown
- Lubbock, TX
Darnell Adams played receiver at Portland State (2014–17).
Career highs
100receiving yards, career highat North Texas, 2015Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2014 | Portland State | 5 | 22 | 4.4 | 0 | 6 |
| 2015 | Portland State | 4 | 100 | 25.0 | 1 | 37 |
| 2017 | Portland State | 5 | 52 | 10.4 | 1 | 22 |
| Career | 14 | 174 | 12.4 | 2 | 37 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Ht | Wt |
|---|---|---|---|---|---|
| 2014 | Portland State | 7 | WR | ||
| 2015 | Portland State | 7 | WR | ||
| 2016 | Portland State | 7 | WR | ||
| 2017 | Portland State | 7 | WR | 6′2″ | 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
| Season | Team | Plays | EPA/play | Pctile | Median | Total | Usage |
|---|---|---|---|---|---|---|---|
| 2014 | Portland State (FCS) | 13 | -0.33 | – | – | -4.3 | – |
| 2015 | Portland State (FCS) | 6 | 1.44 | – | – | 8.7 | – |
| 2017 | Portland State (FCS) | 9 | 0.74 | – | – | 6.7 | – |
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 Portland State 2 games, 5 catches, 52 yards, 1 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Aug 26 | at BYU | L 6–20 | 2 | 11 | 1 | 7 |
| Sep 2 | at Oregon State | L 32–35 | 3 | 41 | 0 | 22 |
No box score in the source for Sep 16 vs. UC Davis; Sep 30 vs. Montana; Oct 7 at Montana State; Oct 14 vs. Northern Arizona; Oct 21 at Idaho State; Oct 28 vs. North Dakota; Nov 5 at Cal Poly; Nov 11 vs. Weber State; Nov 18 at Eastern Washington, so those games are not listed.
2015 Portland State 1 game, 4 catches, 100 yards, 1 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Oct 10 | at North Texas | W 66–7 | 4 | 100 | 1 | 37 |
No box score in the source for Sep 12 at Idaho State; Sep 26 vs. Western Oregon; Oct 3 vs. North Dakota; Oct 17 vs. Montana State; Oct 25 at Cal Poly; Oct 31 vs. Montana; Nov 7 at Northern Colorado; Nov 14 vs. Southern Utah; Nov 21 at Eastern Washington; Dec 6 vs. Northern Iowa, so those games are not listed.
2014 Portland State 2 games, 5 catches, 22 yards
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Aug 30 | atOregon State | L 14–29 | 2 | 8 | 0 | 5 |
| Sep 13 | at Washington State | L 21–59 | 3 | 14 | 0 | 6 |
No box score in the source for Sep 7 vs. Western Oregon; Sep 21 at Cal Poly; Oct 4 vs. UC Davis; Oct 11 at North Dakota; Oct 18 vs. Northern Arizona; Oct 25 at Weber State; Nov 1 vs. Idaho State; Nov 8 at Montana State; Nov 15 at Sacramento State; Nov 22 vs. Eastern Washington, so those games are not listed.
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.