Receiver, Virginia, 2013–17
Andre Levrone
- Number
- No. 14
- Height
- 6′3″
- Weight
- 225 lb
- Hometown
- Laurel, MD
Andre Levrone played receiver at Virginia (2013–17).
Career highs
6catches, career highat Louisville, 2017141receiving yards, career highat Boise State, 20172receiving touchdowns, career hightwice; last vs. Georgia Tech, 2017Receiving
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Ht | Wt |
|---|---|---|---|---|---|
| 2013 | Virginia | 14 | WR | ||
| 2014 | Virginia | 14 | WR | ||
| 2015 | Virginia | 14 | WR | ||
| 2016 | Virginia | 14 | WR | ||
| 2017 | Virginia | 14 | WR | 6′3″ | 225 |
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 | Virginia | 30 | 0.41 | 34th (n=496) | 0.52 | 12.4 | 5% |
| 2015 | Virginia | 5 | -0.18 | – | – | -0.9 | – |
| 2016 | Virginia | 13 | 0.23 | – | – | 3.0 | – |
| 2017 | Virginia | 61 | 0.63 | 67th (n=507) | 0.52 | 38.1 | 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
2017 Virginia 12 games, 34 catches, 689 yards, 7 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 2 | vs. | W 28–10 | 2 | 56 | 1 | 34 |
| Sep 9 | vs. | L 17–34 | 2 | 24 | 0 | 19 |
| Sep 16 | vs. | W 38–18 | 4 | 127 | 1 | 73 |
| Sep 22 | at | W 42–23 | 5 | 141 | 2 | 64 |
| Oct 7 | vs. | W 28–21 | 2 | 29 | 0 | 25 |
| Oct 21 | vs. | L 10–41 | 1 | 9 | 0 | 9 |
| Oct 28 | at | L 14–31 | 2 | 21 | 0 | 16 |
| Nov 4 | vs. | W 40–36 | 3 | 67 | 2 | 34 |
| Nov 11 | at | L 21–38 | 6 | 92 | 0 | 30 |
| Nov 18 | at | L 28–44 | 2 | 37 | 1 | 33 |
| Nov 24 | vs. | L 0–10 | 2 | 59 | 0 | 51 |
| Dec 28 ✦ | at | L 7–49 | 3 | 27 | 0 | 12 |
2016 Virginia 4 games, 8 catches, 126 yards
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Oct 1 | at | W 34–20 | 2 | 65 | 0 | 33 |
| Oct 22 | vs. | L 14–35 | 2 | 22 | 0 | 16 |
| Oct 29 | vs. | L 25–32 | 2 | 19 | 0 | 11 |
| Nov 19 | at | L 17–31 | 2 | 20 | 0 | 12 |
2015 Virginia 1 game, 2 catches, 16 yards
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 5 | at | L 16–34 | 2 | 16 | 0 | 10 |
2014 Virginia 8 games, 15 catches, 248 yards, 2 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Aug 30 | vs. | L 20–28 | 3 | 75 | 1 | 29 |
| Sep 6 | vs. | W 45–13 | 1 | 4 | 0 | 4 |
| Sep 20 | at | L 33–41 | 3 | 46 | 0 | 20 |
| Sep 27 | vs. | W 45–13 | 2 | 53 | 0 | 29 |
| Oct 18 | at | L 13–20 | 2 | 26 | 0 | 21 |
| Nov 8 | at | L 20–34 | 1 | 16 | 1 | 16 |
| Nov 22 | vs. | W 30–13 | 2 | 24 | 0 | 19 |
| Nov 28 | at | L 20–24 | 1 | 4 | 0 | 4 |
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.
