Tight end, Pittsburgh, 2013–16
Jaymar Parrish
- Number
- No. 31
- Height
- 6′2″
- Hometown
- Monroeville, PA
Jaymar Parrish played tight end at Pittsburgh (2013–16).
Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2013 | Pittsburgh | 7 | 40 | 5.7 | 0 | 9 |
| 2014 | Pittsburgh | 4 | 25 | 6.3 | 0 | 9 |
| 2015 | Pittsburgh | 1 | 3 | 3.0 | 0 | 3 |
| 2016 | Pittsburgh | 4 | 78 | 19.5 | 0 | 44 |
| Career | 16 | 146 | 9.1 | 0 | 44 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Ht |
|---|---|---|---|---|
| 2013 | Pittsburgh | 31 | TE | |
| 2014 | Pittsburgh | 31 | TE | |
| 2015 | Pittsburgh | 31 | TE | |
| 2016 | Pittsburgh | 31 | TE | 6′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
| Season | Team | Plays | EPA/play | Pctile | Median | Total | Usage |
|---|---|---|---|---|---|---|---|
| 2013 | Pittsburgh | 11 | 0.27 | – | – | 3.0 | – |
| 2014 | Pittsburgh | 5 | 0.71 | – | – | 3.6 | – |
| 2015 | Pittsburgh | 1 | -0.20 | – | – | -0.2 | – |
| 2016 | Pittsburgh | 5 | 1.48 | – | – | 7.4 | – |
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
2016 Pittsburgh 6 games, 4 catches, 78 yards
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Sep 3 | vs. Villanova | W 28–7 | 1 | 4 | 0 | 4 | – |
| Sep 10 | vs. Penn State | W 42–39 | – | – | – | – | – |
| Sep 24 | at North Carolina | L 36–37 | 1 | 22 | 0 | 22 | – |
| Oct 1 | vs. Marshall | W 43–27 | 1 | 8 | 0 | 8 | – |
| Nov 5 | at Miami | L 28–51 | – | – | – | – | – |
| Nov 12 | at Clemson | W 43–42 | 1 | 44 | 0 | 44 | – |
2015 Pittsburgh 1 game, 1 catch, 3 yards
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Oct 10 | vs. Virginia | W 26–19 | 1 | 3 | 0 | 3 | – |
2014 Pittsburgh 5 games, 4 catches, 25 yards
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Sep 13 | at Florida International | W 42–25 | – | – | – | – | – |
| Sep 20 | vs. Iowa | L 20–24 | 1 | 4 | 0 | 4 | – |
| Sep 27 | vs. Akron | L 10–21 | 2 | 13 | 0 | 9 | – |
| Nov 1 | vs. Duke | L 48–51 | 1 | 8 | 0 | 8 | – |
| Nov 22 | vs. Syracuse | W 30–7 | – | – | – | – | – |
2013 Pittsburgh 7 games, 7 catches, 40 yards
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Sep 2 | vs. Florida State | L 13–41 | 1 | 7 | 0 | 7 | – |
| Oct 26 | at Navy | L 21–24 | 1 | 5 | 0 | 5 | 5 |
| Nov 9 | vs. Notre Dame | W 28–21 | 1 | 4 | 0 | 4 | 2 |
| Nov 16 | vs.North Carolina | L 27–34 | – | – | – | – | 1 |
| Nov 23 | atSyracuse | W 17–16 | 3 | 19 | 0 | 9 | – |
| Nov 29 | vs.Miami | L 31–41 | 1 | 5 | 0 | 5 | – |
| Dec 26 ✦ | vs. Bowling Green | W 30–27 | – | – | – | – | 2 |
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.