Running back, Duke, 2008–11
Jay Hollingsworth
- Number
- No. 27
- Height
- 5′10″
- Hometown
- Sanford, NC
Jay Hollingsworth played running back at Duke (2008–11).
Career highs
7catches, career highvs. NC State, 200880receiving yards, career highvs. NC State, 2008Rushing
Receiving
Season lines from CollegeFootballData, regular season and bowls. * That team-season’s player lines are missing part of the team’s yards in our source, so these numbers may be short.
On the roster
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
2011 Duke 9 games, 107 rushing yards, 1 TD
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Sep 3 | vs. Richmond | L 21–23 | 2 | 5 | 0 | 1 | 4 | 0 |
| Sep 10 | vs. Stanford | L 14–44 | 3 | 10 | 0 | 3 | 37 | 0 |
| Sep 17 | at Boston College | W 20–19 | 1 | 1 | 0 | – | – | – |
| Sep 24 | vs. Tulane | W 48–27 | 6 | 30 | 1 | 2 | 46 | 0 |
| Oct 1 | at Florida International | W 31–27 | 1 | 2 | 0 | 2 | 9 | 0 |
| Oct 15 | vs. Florida State | L 16–41 | 4 | 21 | 0 | 3 | 18 | 0 |
| Oct 22 | vs. Wake Forest | L 23–24 | 5 | 15 | 0 | 2 | 11 | 0 |
| Nov 5 | at Miami | L 14–49 | 4 | 24 | 0 | – | – | – |
| Nov 19 | vs. Georgia Tech | L 31–38 | 1 | −1 | 0 | – | – | – |
2010 Duke 10 games, 175 rushing yards, 2 TD
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Sep 4 | vs. Elon | W 41–27 | 10 | 10 | 1 | – | – | – |
| Sep 11 | atWake Forest | L 48–54 | 1 | 8 | 0 | – | – | – |
| Sep 18 | vs. Alabama | L 13–62 | 2 | 4 | 0 | 1 | 2 | 0 |
| Oct 2 | at Maryland | L 16–21 | 3 | 2 | 0 | 2 | 9 | 0 |
| Oct 16 | vs.Miami | L 13–28 | 10 | 69 | 0 | 1 | 5 | 0 |
| Oct 23 | at Virginia Tech | L 7–44 | 4 | 26 | 1 | 1 | 13 | 0 |
| Oct 30 | at Navy | W 34–31 | 7 | 21 | 0 | – | – | – |
| Nov 6 | vs. Virginia | W 55–48 | 1 | 4 | 0 | – | – | – |
| Nov 13 | vs.Boston College | L 16–21 | 2 | 0 | 0 | – | – | – |
| Nov 20 | atGeorgia Tech | L 20–30 | 5 | 31 | 0 | – | – | – |
2009 Duke 11 games, 179 rushing yards
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Sep 5 | vs.Richmond | L 16–24 | 3 | 7 | 0 | 4 | 15 | 0 |
| Sep 12 | at Army | W 35–19 | 5 | 24 | 0 | – | – | – |
| Sep 19 | at Kansas | L 16–44 | 9 | 38 | 0 | 2 | 0 | 0 |
| Sep 26 | vs. North Carolina Central | W 49–14 | – | – | – | 1 | 2 | 0 |
| Oct 10 | at NC State | W 49–28 | – | – | – | 1 | −2 | 0 |
| Oct 24 | vs.Maryland | W 17–13 | 6 | 10 | 0 | 3 | 34 | 0 |
| Oct 31 | atVirginia | W 28–17 | 12 | 39 | 0 | 1 | 9 | 0 |
| Nov 7 | at North Carolina | L 6–19 | 1 | 1 | 0 | 2 | 6 | 0 |
| Nov 14 | vs.Georgia Tech | L 10–49 | 2 | 9 | 0 | 1 | −1 | 0 |
| Nov 21 | atMiami | L 16–34 | 10 | 32 | 0 | 2 | 24 | 0 |
| Nov 28 | vs.Wake Forest | L 34–45 | 6 | 19 | 0 | – | – | – |
2008 Duke 12 games, 399 rushing yards, 1 TD
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Aug 30 | vs. James Madison | W 31–7 | 15 | 46 | 0 | – | – | – |
| Sep 6 | vs. Northwestern | L 20–24 | 11 | 41 | 0 | 2 | 17 | 0 |
| Sep 13 | vs.Navy | W 41–31 | 3 | 8 | 0 | 1 | 2 | 0 |
| Sep 27 | vs.Virginia | W 31–3 | 15 | 59 | 0 | 2 | 8 | 1 |
| Oct 4 | atGeorgia Tech | L 0–27 | 6 | 12 | 0 | 2 | 9 | 0 |
| Oct 18 | vs.Miami | L 31–49 | 4 | 17 | 0 | – | – | – |
| Oct 25 | at Vanderbilt | W 10–7 | 10 | 39 | 0 | 1 | 0 | 0 |
| Nov 1 | atWake Forest | L 30–33 | 15 | 67 | 1 | 1 | 2 | 0 |
| Nov 8 | vs.NC State | L 17–27 | 7 | 23 | 0 | 7 | 80 | 1 |
| Nov 15 | at Clemson | L 7–31 | 5 | 13 | 0 | 3 | 9 | 0 |
| Nov 22 | atVirginia Tech | L 3–14 | 8 | 24 | 0 | – | – | – |
| Nov 29 | vs.North Carolina | L 20–28 | 9 | 50 | 0 | 6 | 61 | 0 |
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.