Receiver, Idaho State, 2015–17
Hagen Graves
- Number
- No. 6
- Height
- 6′0″
- Weight
- 185 lb
- Hometown
- Lubbock, TX
Hagen Graves played receiver at Idaho State (2015–17).
Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2015 | Idaho State | 1 | 18 | 18.0 | 0 | 18 |
| 2016 | Idaho State | 6 | 27 | 4.5 | 0 | 7 |
| 2017 | Idaho State | 7 | 101 | 14.4 | 1 | 24 |
| Career | 14 | 146 | 10.4 | 1 | 24 | |
Returns
| Season | Team | KR | Yds | TD |
|---|---|---|---|---|
| 2015 | Idaho State | 5 | 106 | 0 |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Ht | Wt |
|---|---|---|---|---|---|
| 2015 | Idaho State | 6 | WR | ||
| 2016 | Idaho State | 6 | WR | ||
| 2017 | Idaho State | 6 | WR | 6′0″ | 185 |
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 | Idaho State (FCS) | 3 | 0.70 | – | – | 2.1 | – |
| 2016 | Idaho State (FCS) | 11 | -0.10 | – | – | -1.1 | – |
| 2017 | Idaho State (FCS) | 8 | 1.73 | – | – | 13.9 | – |
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 Idaho State 2 games, 7 catches, 101 yards, 1 TD
| Date | Opponent | Result | Rec | Rec yds | Rec TD | KR | Yds |
|---|---|---|---|---|---|---|---|
| Sep 7 | at Utah State | L 13–51 | 5 | 70 | 0 | – | – |
| Sep 16 | at Nevada | W 30–28 | 2 | 31 | 1 | – | – |
No box score in the source for Sep 1 vs. Western Oregon; Sep 23 at Northern Colorado; Sep 30 vs. Cal Poly; Oct 7 vs. Montana; Oct 15 at Sacramento State; Oct 21 vs. Portland State; Oct 28 at Montana State; Nov 4 vs. UC Davis; Nov 18 at Weber State, so those games are not listed.
2016 Idaho State 2 games, 6 catches, 27 yards
| Date | Opponent | Result | Rec | Rec yds | Rec TD | KR | Yds |
|---|---|---|---|---|---|---|---|
| Sep 10 | at Colorado | L 7–56 | 4 | 15 | 0 | – | – |
| Sep 17 | at Oregon State | L 7–37 | 2 | 12 | 0 | – | – |
No box score in the source for Sep 24 vs. Sacramento State; Oct 1 at Portland State; Oct 15 at Northern Arizona; Oct 22 vs. North Dakota; Oct 29 vs. Southern Utah; Nov 5 at Montana; Nov 12 at Eastern Washington; Nov 19 vs. Weber State, so those games are not listed.
2015 Idaho State 1 game, 5 returns, 106 yards
| Date | Opponent | Result | Rec | Rec yds | Rec TD | KR | Yds |
|---|---|---|---|---|---|---|---|
| Sep 18 | at Boise State | L 0–52 | 1 | 18 | 0 | 5 | 106 |
No box score in the source for Sep 5 vs. Black Hills State; Sep 12 vs. Portland State; Oct 4 at Cal Poly; Oct 10 at North Dakota; Oct 17 vs. Eastern Washington; Oct 25 at Sacramento State; Nov 7 vs. Montana; Nov 14 vs. Montana State; Nov 21 at Weber State, 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.