Receiver, North Carolina, 2016–19
Corey Bell Jr.
- Number
- No. 9
- Height
- 5′9″
- Weight
- 190 lb
- Class (2019)
- Senior
- Hometown
- Charlotte, NC
Corey Bell Jr. played receiver at North Carolina (2016–19).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | Int | PD | Hur |
|---|---|---|---|---|---|---|---|---|
| 2016 | North Carolina | 16 | 11 | 1 | 0 | 0 | 0 | 0 |
| 2017 | North Carolina | 5 | 3 | 0.5 | 0 | 0 | 0 | 0 |
| 2018 | North Carolina | 4 | 3 | 0 | 0 | 1 | 3 | 0 |
| 2019 | North Carolina | 1 | 0 | 0 | 0 | 0 | 0 | 0 |
| Career | 26 | 17 | 1.5 | 0 | 1 | 3 | 0 | |
Season lines from CollegeFootballData, regular season and bowls. 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 |
|---|---|---|---|---|---|---|
| 2016 | North Carolina | 9 | WR | Fr. | ||
| 2017 | North Carolina | 9 | WR | So. | ||
| 2018 | North Carolina | 9 | WR | Jr. | ||
| 2019 | North Carolina | 9 | WR | Sr. | 5′9″ | 190 |
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 |
|---|---|---|---|---|---|---|---|
| 2018 | North Carolina | 1 | -0.70 | – | – | -0.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
2019 North Carolina 1 game, 1 tackle
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 13 | at Wake Forest | L 18–24 | 1 | 0 | 0 | 0 | 0 | 0 |
2018 North Carolina 4 games, 4 tackles, 1 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 8 | at East Carolina | L 19–41 | 1 | 1 | 0 | 0 | 0 | 0 |
| Nov 10 | at Duke | L 35–42 | 0 | 0 | 0 | 0 | 0 | 1 |
| Nov 17 | vs. Western Carolina | W 49–26 | 2 | 1 | 0 | 0 | 0 | 1 |
| Nov 24 | vs. NC State | L 28–34 | 1 | 1 | 0 | 0 | 1 | 1 |
2017 North Carolina 3 games, 5 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 2 | vs. California | L 30–35 | 3 | 2 | 0.5 | 0 | 0 | 0 |
| Sep 9 | vs. Louisville | L 35–47 | 1 | 0 | 0 | 0 | 0 | 0 |
| Sep 16 | at Old Dominion | W 53–23 | 1 | 1 | 0 | 0 | 0 | 0 |
2016 North Carolina 7 games, 16 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 24 | vs. Pittsburgh | W 37–36 | 1 | 0 | 0 | 0 | 0 | 0 |
| Oct 8 | vs. Virginia Tech | L 3–34 | 1 | 1 | 0 | 0 | 0 | 0 |
| Oct 15 | at Miami | W 20–13 | 4 | 4 | 0 | 0 | 0 | 0 |
| Nov 10 | atDuke | L 27–28 | 2 | 1 | 0 | 0 | 0 | 0 |
| Nov 19 | vs. The Citadel | W 41–7 | 2 | 2 | 1 | 0 | 0 | 0 |
| Nov 25 | vs.NC State | L 21–28 | 4 | 3 | 0 | 0 | 0 | 0 |
| Dec 30 ✦ | vs. Stanford | L 23–25 | 2 | 0 | 0 | 0 | 0 | 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.