Manasseh Garner, 2017
Photo: C Watts, CC BY 2.0, via Wikimedia Commons

Receiver, Pittsburgh (from Wisconsin), 2010–⁠14

Manasseh Garner

Lettered 2013–⁠14 (school media guide)

Number
No. 82
Height
6′2″
Hometown
Pittsburgh, PA
Born
Mar 11, 1992, in Pittsburgh, Pennsylvania

Wikipedia readers: about 104 a month over the past year

Manasseh Garner played receiver at Wisconsin (2010–⁠11) and Pittsburgh (2013–⁠14).

Career highs

7catches, career highat Syracuse, 2013

Team titles: Big Ten champions, 2010 and 2011

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2011Wisconsin24522.5027
2013Pittsburgh3339111.8328
2014Pittsburgh1720111.8222
Career5263712.3528

Season lines from CollegeFootballData, regular season and bowls.

Defense before 2016

SeasonTeamGSoloAstTklTFL
2010Wisconsin464101
2013NPittsburgh132020
On file84121

Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources, marked by season: unmarked, cfbstats.com (Open Data Commons Attribution License), its game lines summed (G: the games he has a line in); N, NCAA statistics, via octonion/football, the season’s official lines (G: games played). A dash: the source has no number for it.

On the roster

SeasonTeamNo.PosHt
2010Wisconsin82WR
2011Wisconsin82WR
2013Pittsburgh82WR
2014Pittsburgh82WR6′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
2013Pittsburgh330.9168th (n=341)0.8130.15%
2014Pittsburgh210.52––11.05%

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 Pittsburgh 8 games, 17 catches, 201 yards, 2 TD
DateOpponentResultRecYdsTDLong
Aug 30vs.DelawareW 62–⁠0224013
Sep 5atBoston CollegeW 30–⁠20122022
Sep 13atFlorida InternationalW 42–⁠2532309
Sep 20vs.IowaL 20–⁠24338022
Sep 27vs.AkronL 10–⁠21332112
Oct 4atVirginiaL 19–⁠24225117
Oct 25vs.Georgia TechL 28–⁠56218011
Nov 1vs.DukeL 48–⁠51119019
2013 Pittsburgh 12 games, 33 catches, 391 yards, 3 TD
DateOpponentResultRecYdsTDLong
Sep 2vs.Florida StateL 13–⁠4121117
Sep 14vs.New MexicoW 49–⁠27226018
Sep 21atDukeW 58–⁠55113013
Oct 12atVirginia TechL 9–⁠19217010
Oct 19vs.Old DominionW 35–⁠24229121
Oct 26atNavyL 21–⁠24229028
Nov 2atGeorgia TechL 10–⁠21316013
Nov 9vs.Notre DameW 28–⁠21223012
Nov 16vs.North CarolinaL 27–⁠34568019
Nov 23atSyracuseW 17–⁠16761116
Nov 29vs.MiamiL 31–⁠41478024
Dec 26 ✦vs.Bowling GreenW 30–⁠27120020
2011 Wisconsin 2 games, 2 catches, 45 yards
DateOpponentResultRecYdsTDLong
Sep 24vs.South DakotaW 59–⁠10127027
Nov 5vs.PurdueW 62–⁠17118018

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

Before the draft

DrillPro day 2015
Height6′2″
Weight234 lb
40-yard dash4.76 s
10-yard split1.63 s
Vertical jump30½″
Broad jump9′10″
Bench press25 reps
3-cone drill7.12 s
20-yard shuttle4.47 s

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.