Tight end, Virginia (from Clemson), 2020–25
Sage Ennis
- Number
- No. 0
- Height
- 6′4″
- Weight
- 245 lb
- Class (2025)
- Senior
- Hometown
- Graceville, FL
Sage Ennis played tight end at Clemson (2020–23) and Virginia (2024–25).
Team titles: ACC champions, 2020 and 2022
Receiving
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2020 | Clemson | 0 | TE | Yr 1 | ||
| 2021 | Clemson | 0 | TE | Yr 2 | ||
| 2022 | Clemson | 0 | TE | Yr 3 | ||
| 2023 | Clemson | 0 | TE | Yr 4 | ||
| 2024 | Virginia | 0 | TE | Yr 5 | ||
| 2025 | Virginia | 0 | TE | Sr. (Yr 6) | 6′4″ | 245 |
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 | Clemson | 1 | 0.39 | – | – | 0.4 | – |
| 2022 | Clemson | 2 | 0.17 | – | – | 0.3 | – |
| 2023 | Clemson | 3 | 0.18 | – | – | 0.5 | – |
| 2024 | Virginia | 1 | -0.50 | – | – | -0.5 | – |
| 2025 | Virginia | 39 | 0.16 | 12th (n=1040) | 0.46 | 6.3 | 5% |
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
2025 Virginia 10 games, 23 catches, 214 yards, 5 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 6 | at NC State | L 31–35 | 2 | 10 | 1 | 7 |
| Sep 20 | vs. Stanford | W 48–20 | 2 | 21 | 1 | 13 |
| Sep 26 | vs. Florida State | W 46–38 | 1 | 6 | 1 | 6 |
| Oct 18 | vs. Washington State | W 22–20 | 2 | 33 | 0 | 23 |
| Oct 25 | at North Carolina | W 17–16 | 2 | 25 | 0 | 16 |
| Nov 1 | at California | W 31–21 | 4 | 40 | 0 | 25 |
| Nov 8 | vs. Wake Forest | L 9–16 | 2 | 20 | 0 | 16 |
| Nov 15 | at Duke | W 34–17 | 1 | 12 | 1 | 12 |
| Nov 29 | vs. Virginia Tech | W 27–7 | 2 | 12 | 1 | 11 |
| Dec 27 ✦ | vs. Missouri | W 13–7 | 5 | 35 | 0 | 15 |
2024 Virginia 1 game, 1 catch, 2 yards
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 7 | atWake Forest | W 31–30 | 1 | 2 | 0 | 2 |
2023 Clemson 3 games, 3 catches, 52 yards
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Oct 7 | vs.Wake Forest | W 17–12 | 1 | 6 | 0 | 6 |
| Oct 28 | atNC State | L 17–24 | 1 | 28 | 0 | 28 |
| Nov 4 | vs. Notre Dame | W 31–23 | 1 | 18 | 0 | 18 |
2022 Clemson 1 game, 2 catches, 17 yards
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Nov 5 | atNotre Dame | L 14–35 | 2 | 17 | 0 | 13 |
2021 Clemson 1 game, 1 catch, 8 yards
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Oct 2 | vs. Boston College | W 19–13 | 1 | 8 | 0 | 8 |
2020 Clemson 1 game, 1 tackle
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Nov 28 | vs. Pittsburgh | W 52–17 | – | – | – | – |
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.