Receiver, Bowling Green, 2013–17
Trevor Roop
Lettered 2015–17 (school media guide)
- Number
- No. 10
- Height
- 5′11″
- Weight
- 202 lb
- Hometown
- Convoy, OH
Trevor Roop played receiver at Bowling Green (2013–17).
Team titles: MAC champions, 2013 and 2015
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2016 | Bowling Green | 4 | 2 | 0 | 0 | 0 | 0 |
| 2017 | Bowling Green | 11 | 5 | 0 | 0 | 0 | 0 |
| Career | 15 | 7 | 0 | 0 | 0 | 0 | |
Season lines from CollegeFootballData, regular season and bowls. * That team-season’s player lines are missing part of the team’s yards in our source, so these numbers may be short.
Defense before 2016
| Season | G | Solo | Ast | Tkl |
|---|---|---|---|---|
| 2015 | 8 of 14 | 2 | 4 | 6 |
Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources: ESPN play-by-play participants, via SportsDataverse: tackles only, counted in the games whose play-by-play names tacklers (G: those games, of his team’s), so part of the season, not its total. A dash: the source has no number for it.
On the roster
| Season | Team | No. | Pos | Ht | Wt |
|---|---|---|---|---|---|
| 2013 | Bowling Green | 10 | WR | ||
| 2014 | Bowling Green | 10 | WR | ||
| 2015 | Bowling Green | 10 | WR | ||
| 2016 | Bowling Green | 10 | WR | ||
| 2017 | Bowling Green | 10 | WR | 5′11″ | 202 |
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 | Bowling Green | 1 | 1.79 | – | – | 1.8 | – |
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 Bowling Green 8 games, 11 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 2 | at Michigan State | L 10–35 | 2 | 0 | 0 | 0 | 0 |
| Sep 9 | vs. South Dakota | L 27–35 | 1 | 0 | 0 | 0 | 0 |
| Sep 16 | at Northwestern | L 7–49 | 1 | 0 | 0 | 0 | 0 |
| Sep 30 | vs. Akron | L 23–34 | 1 | 1 | 0 | 0 | 0 |
| Oct 14 | vs. Ohio | L 30–48 | 2 | 2 | 0 | 0 | 0 |
| Oct 31 | at Kent State | W 44–16 | 1 | 0 | 0 | 0 | 0 |
| Nov 15 | vs. Toledo | L 37–66 | 2 | 2 | 0 | 0 | 0 |
| Nov 21 | at Eastern Michigan | L 31–34 | 1 | 0 | 0 | 0 | 0 |
2016 Bowling Green 3 games, 4 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 17 | vs. Middle Tennessee | L 21–41 | 2 | 1 | 0 | 0 | 0 |
| Sep 24 | at Memphis | L 3–77 | 1 | 0 | 0 | 0 | 0 |
| Oct 22 | vs. Miami (OH) | L 26–40 | 1 | 1 | 0 | 0 | 0 |
2014 Bowling Green 1 game, 1 catch, 10 yards
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 6 | vs. VMI | W 48–7 | – | – | – | – | – |
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.