Receiver, Southern Utah, 2021–22
Ethan Bolingbroke
- Number
- No. 83
- Height
- 5′10″
- Weight
- 175 lb
- Class (2022)
- Junior
- Hometown
- Sandy, UT
Ethan Bolingbroke played receiver at Southern Utah (2021–22).
Career highs
6catches, career hightwice; last vs. Utah Tech, 2022Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2021* | Southern Utah | 3 | 30 | 10.0 | 0 | 12 |
| 2022 | Southern Utah | 31 | 330 | 10.6 | 2 | 44 |
| Career | 34 | 360 | 10.6 | 2 | 44 | |
Returns
| Season | Team | KR | Yds | TD | PR | Yds | TD |
|---|---|---|---|---|---|---|---|
| 2021* | Southern Utah | – | – | – | 1 | 0 | 0 |
| 2022 | Southern Utah | 2 | 31 | 0 | 24 | 187 | 0 |
| Career | 2 | 31 | 0 | 25 | 187 | 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. A dash: the source has no number for that season (often an FCS season), and career totals count only the numbers on file.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2021 | Southern Utah | 83 | WR | So. | ||
| 2022 | Southern Utah | 83 | WR | Jr. | 5′10″ | 175 |
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 |
|---|---|---|---|---|---|---|---|
| 2021 | Southern Utah (FCS) | 1 | 0.72 | – | – | 0.7 | – |
| 2022 | Southern Utah (FCS) | 27 | 0.17 | – | – | 4.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
2022 Southern Utah 11 games, 31 catches, 330 yards, 2 TD
| Date | Opponent | Result | Rec | Rec yds | Rec TD | KR | Yds | PR |
|---|---|---|---|---|---|---|---|---|
| Sep 1 | vs. St. Thomas (MN) | W 44–13 | 2 | 13 | 0 | – | – | 2 |
| Sep 10 | at Utah | L 7–73 | 1 | 2 | 0 | – | – | 1 |
| Sep 17 | at Western Illinois | W 17–10 | 6 | 70 | 0 | – | – | 3 |
| Sep 24 | vs. Utah Tech | W 31–17 | 6 | 61 | 1 | 1 | 11 | 1 |
| Oct 1 | at Eastern Kentucky | L 28–35 | 4 | 55 | 0 | – | – | 1 |
| Oct 8 | vs. Tarleton State | L 40–42 | 2 | 32 | 0 | – | – | 3 |
| Oct 15 | at Abilene Christian | L 18–21 | 2 | 15 | 1 | – | – | 5 |
| Oct 22 | vs. Stephen F. Austin | L 38–41 | 1 | 13 | 0 | – | – | 1 |
| Nov 5 | atUtah Tech | L 36–48 | 1 | 10 | 0 | 1 | 20 | 1 |
| Nov 12 | vs.Lincoln (CA) | W 55–0 | 5 | 52 | 0 | – | – | 3 |
| Nov 19 | at Sam Houston | W 17–7 | 1 | 7 | 0 | – | – | 3 |
2021 Southern Utah 2 games, 3 catches, 30 yards
| Date | Opponent | Result | Rec | Rec yds | Rec TD | KR | Yds | PR |
|---|---|---|---|---|---|---|---|---|
| Aug 28 | at San José State | L 14–45 | 2 | 18 | 0 | – | – | 1 |
| Sep 2 | at Arizona State | L 14–41 | 1 | 12 | 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.