Tight end, North Carolina, 2011–⁠14

Eric Albright

Number
No. 49
Height
6′6″
Hometown
Raleigh, NC

Eric Albright played tight end at North Carolina (2011–⁠14).

Receiving

SeasonTeamRecYdsAvgTDLong
2014North Carolina29648.0167

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHt
2011North Carolina49TE
2012North Carolina49TE
2013North Carolina49TE
2014North Carolina49TE6′6″

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

SeasonTeamPlaysEPA/playPctileMedianTotalUsage
2014North Carolina24.57––9.1–

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

2014 North Carolina 2 games, 2 catches, 96 yards, 1 TD
DateOpponentResultRecYdsTDLong
Sep 20atEast CarolinaL 41–⁠70129129
Sep 27atClemsonL 35–⁠50167067

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.