Receiver, Louisville, 2015–16
Jamari Staples
- Number
- No. 2
- Height
- 6′4″
- Hometown
- Lineville, AL
Jamari Staples played receiver at Louisville (2015–16).
Career highs
10catches, career highat Wake Forest, 2015194receiving yards, career highat Pittsburgh, 20152receiving touchdowns, career highat Wake Forest, 2015Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2015 | Louisville | 35 | 599 | 17.1 | 3 | 57 |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Ht |
|---|---|---|---|---|
| 2015 | Louisville | 2 | WR | |
| 2016 | Louisville | 2 | WR | 6′4″ |
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.
Game by game
2015 Louisville 7 games, 35 catches, 599 yards, 3 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Oct 3 | at NC State | W 20–13 | 2 | 22 | 0 | 11 |
| Oct 17 | at Florida State | L 21–41 | 4 | 56 | 0 | 25 |
| Oct 24 | vs. Boston College | W 17–14 | 4 | 96 | 0 | 53 |
| Oct 30 | at Wake Forest | W 20–19 | 10 | 133 | 2 | 23 |
| Nov 7 | vs. Syracuse | W 41–17 | 4 | 79 | 0 | 26 |
| Nov 14 | vs. Virginia | W 38–31 | 2 | 19 | 0 | 11 |
| Nov 21 | at Pittsburgh | L 34–45 | 9 | 194 | 1 | 57 |
Box scores from CollegeFootballData, 2004 on. ✦ postseason; ★ a career high on file.
Before the draft
| Drill | Combine 2017 | Combine or pro day 2017 |
|---|---|---|
| Height | 6′2⅞″ | |
| Weight | 195 lb | |
| Arm length | 33½″ | |
| Hand size | 9½″ | |
| 40-yard dash | 4.51 s | |
| 10-yard split | 1.54 s | |
| Vertical jump | 36″ | |
| Broad jump | 10′10″ | |
| 20-yard shuttle | 4.14 s |
Combine or pro day: the source doesn’t say which. 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.