Receiver, Rutgers, 2010–⁠13

Brandon Coleman

Lettered 2011–⁠13 (school media guide)

Number
No. 17
Height
6′6″
Hometown
Accokeek, MD

Brandon Coleman played receiver at Rutgers (2010–⁠13).

At a glance

Best season
718
Receiving yards, 2012 (Rutgers, 9–⁠4)
Best game
223 yards
At UConn, week 13, 2011: No. 2 receiving game in FBS that week

Career highs

9catches, career highat Fresno State, 2013223receiving yards, career highat UConn, 20112receiving touchdowns, career highfive times; last at Fresno State, 2013

Team titles: Big East champions, 2012

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2011Rutgers1755232.5692
2012Rutgers4371816.71085
2013Rutgers3453815.8456
Career941,80819.22092

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHt
2010Rutgers17WR
2011Rutgers17WR
2012Rutgers17WR
2013Rutgers17WR6′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
2013Rutgers311.5299th (n=341)0.8147.04%

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

2013 Rutgers 12 games, 34 catches, 538 yards, 4 TD
DateOpponentResultRecYdsTDLong
Aug 29atFresno StateL 51–⁠52994228
Sep 7vs.Norfolk StateW 38–⁠0230026
Sep 14vs.Eastern MichiganW 28–⁠10115015
Sep 21vs.ArkansasW 28–⁠24125025
Oct 5atSMUW 55–⁠52256056
Oct 10atLouisvilleL 10–⁠24566021
Nov 2vs.TempleW 23–⁠20240030
Nov 16vs.CincinnatiL 17–⁠52677126
Nov 21atUCFL 17–⁠41120020
Nov 30atUConnL 17–⁠28236019
Dec 7vs.South FloridaW 31–⁠6114014
Dec 28 ✦vs.Notre DameL 16–⁠29265151
2012 Rutgers 13 games, 43 catches, 718 yards, 10 TD
DateOpponentResultRecYdsTDLong
Sep 1atTulaneW 24–⁠12241143
Sep 8vs.HowardW 26–⁠0248232
Sep 13atSouth FloridaW 23–⁠13229017
Sep 22atArkansasW 35–⁠26689238
Oct 6vs.UConnW 19–⁠3671019
Oct 13vs.SyracuseW 23–⁠156104043
Oct 20atTempleW 35–⁠10217017
Oct 27vs.Kent StateL 23–⁠35551124
Nov 10vs.ArmyW 28–⁠7353231
Nov 17atCincinnatiW 10–⁠3249041
Nov 24atPittsburghL 6–⁠27111111
Nov 29vs.LouisvilleL 17–⁠202100185
Dec 28 ✦vs.Virginia TechL 10–⁠13455043
2011 Rutgers 9 games, 17 catches, 552 yards, 6 TD
DateOpponentResultRecYdsTDLong
Sep 1vs.North Carolina CentralW 48–⁠0144144
Sep 10atNorth CarolinaL 22–⁠24119019
Sep 24vs.OhioW 38–⁠261909
Oct 29vs.West VirginiaL 31–⁠41125025
Nov 5vs.South FloridaW 20–⁠17375134
Nov 12vs.ArmyW 27–⁠12138138
Nov 19vs.CincinnatiW 20–⁠3233019
Nov 26atUConnL 22–⁠406223292
Dec 30 ✦vs.Iowa StateW 27–⁠13186186

Box scores from CollegeFootballData, 2004 on. ✦ postseason; ★ a career high on file.

Before the draft

DrillCombine 2014
Height6′6″
Weight225 lb
Arm length34″
Hand size9¼″
Wingspan81⅝″W
40-yard dash4.56 s
10-yard split1.66 sW
Vertical jump32½″
Bench press21 reps
3-cone drill7.33 s
20-yard shuttle4.51 s

Unmarked: Combine and pro day results compiled by array-carpenter (nfl-draft-data); W: Pre-draft measurables: Wikipedia (CC BY-SA).

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.