Punter, North Carolina, 2012–16
Joey Mangili
- Number
- No. 14
- Height
- 6′3″
- Hometown
- Durham, NC
Joey Mangili played punter at North Carolina (2012–16).
Punting
| Season | Team | Punts | Yds | Avg | Long | In 20 |
|---|---|---|---|---|---|---|
| 2013 | North Carolina | 2 | 83 | 41.5 | 44 | 0 |
| 2014 | North Carolina | 2 | 49 | 24.5 | 29 | 1 |
| 2015 | North Carolina | 24 | 978 | 40.8 | 51 | 0 |
| Career | 28 | 1,110 | 39.6 | 51 | 1 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Ht |
|---|---|---|---|---|
| 2012 | North Carolina | 14 | P | |
| 2013 | North Carolina | 14 | P | |
| 2014 | North Carolina | 14 | P | |
| 2015 | North Carolina | 14 | P | |
| 2016 | North Carolina | 14 | P | 6′3″ |
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 North Carolina 7 games, 24 punts, 40.8 average
| Date | Opponent | Result | Punts | Yds | Long | In 20 |
|---|---|---|---|---|---|---|
| Oct 29 | at Pittsburgh | W 26–19 | 1 | 36 | 36 | 0 |
| Nov 7 | vs. Duke | W 66–31 | 2 | 91 | 49 | 0 |
| Nov 14 | vs. Miami | W 59–21 | 3 | 125 | 46 | 0 |
| Nov 21 | at Virginia Tech | W 30–27 | 8 | 321 | 48 | 0 |
| Nov 28 | at NC State | W 45–34 | 1 | 33 | 33 | 0 |
| Dec 5 | vs. Clemson | L 37–45 | 6 | 249 | 51 | 0 |
| Dec 29 ✦ | vs. Baylor | L 38–49 | 3 | 123 | 48 | 0 |
2014 North Carolina 1 game, 2 punts, 24.5 average
| Date | Opponent | Result | Punts | Yds | Long | In 20 |
|---|---|---|---|---|---|---|
| Dec 26 ✦ | vs. Rutgers | L 21–40 | 2 | 49 | 29 | 1 |
2013 North Carolina 1 game, 2 punts, 41.5 average
| Date | Opponent | Result | Punts | Yds | Long | In 20 |
|---|---|---|---|---|---|---|
| Nov 9 | vs. Virginia | W 45–14 | 2 | 83 | 44 | 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.