Receiver, Boston College and UConn, 2010–⁠14

Shakim Phillips

Lettered 2014 (school media guide)

Number
No. 11
Height
6′2″
Hometown
Paterson, NJ

Shakim Phillips played receiver at Boston College (2010–⁠11), UConn (2012), Boston College (2012), UConn (2012–⁠13), Boston College (2013), UConn (2013) and Boston College (2014).

Career highs

10catches, career highvs. Maryland, 2013178receiving yards, career highvs. Maryland, 20132receiving touchdowns, career highvs. Towson, 2013

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2010Boston College199.009
2012UConn3239912.5125
2013UConn2840614.5375
2014Boston College1328221.7449
Career741,09614.8875

Returns

SeasonTeamKRYdsTD
2010Boston College4630
2013UConn51000
Career91630

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHt
2010Boston College11WR
2011Boston College11WR
2012UConn11WR
2012Boston College11WR
2013UConn11WR
2013Boston College11WR
2014Boston College11WR6′2″

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
2013UConn300.7643rd (n=341)0.8122.68%
2014Boston College240.86––20.65%

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 Boston College 8 games, 13 catches, 282 yards, 4 TD
DateOpponentResultRecYdsTDLongRush
Sep 5vs.PittsburghL 20–⁠30478148–
Sep 13vs.USCW 37–⁠31117017–
Sep 20vs.MaineW 40–⁠101707−2
Oct 25atWake ForestW 23–⁠17137137–
Nov 1atVirginia TechW 33–⁠31124024–
Nov 22atFlorida StateL 17–⁠20149149–
Nov 29vs.SyracuseW 28–⁠7130030–
Dec 27 ✦vs.Penn StateL 30–⁠31340119–
2013 UConn 6 games, 28 catches, 406 yards, 3 TD
DateOpponentResultRecYdsTDLongRush
Aug 29vs.TowsonL 18–⁠33577231–
Sep 14vs.MarylandL 21–⁠3210178175–
Oct 19atCincinnatiL 16–⁠41338021–
Oct 26atUCFL 17–⁠6242109–
Nov 8vs.LouisvilleL 10–⁠31219015–
Nov 16atSMUL 21–⁠38473034–
2012 UConn 10 games, 32 catches, 399 yards, 1 TD
DateOpponentResultRecYdsTDLongRush
Aug 30vs.MassachusettsW 37–⁠0221015–
Sep 8vs.NC StateL 7–⁠101909–
Sep 22atWestern MichiganL 24–⁠30442013–
Sep 29vs.BuffaloW 24–⁠17118018–
Oct 13vs.TempleL 14–⁠177100025–
Oct 19atSyracuseL 10–⁠40236023–
Nov 3atSouth FloridaL 6–⁠13121021–
Nov 9vs.PittsburghW 24–⁠17552017–
Nov 24atLouisvilleW 23–⁠202714–
Dec 1vs.CincinnatiL 17–⁠34793019–
2010 Boston College 2 games, 1 catch, 9 yards
DateOpponentResultRecYdsTDLongRush
Oct 16atFlorida StateL 19–⁠241909–
Oct 23vs.MarylandL 21–⁠24–––––

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

Before the draft

DrillPro day 2015
Height6′1″
Weight206 lb
Arm length32⅜″
Hand size9½″
40-yard dash4.42 s
Vertical jump39″
Broad jump10′7″
Bench press17 reps
3-cone drill6.97 s
20-yard shuttle4.33 s

Combine and pro day results compiled by array-carpenter (nfl-draft-data).

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.