Tight end, NC State, 2009–⁠12

Mario Carter

Lettered 2011–⁠12 (school media guide)

Number
No. 87
Height
6′4″
Hometown
Pittsburgh, PA

Mario Carter played tight end at NC State (2009–⁠12).

Career highs

7catches, career highat Clemson, 2012105receiving yards, career highat Clemson, 2012

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2010NC State3258.3014
2011*NC State9849.3123
2012NC State3436710.8235
Career4647610.3335

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

SeasonTeamNo.PosHt
2009NC State87TE
2010NC State87TE
2011NC State87TE
2012NC State87TE6′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

2012 NC State 12 games, 34 catches, 367 yards, 2 TD
DateOpponentResultRecYdsTDLong
Aug 31vs.TennesseeL 21–⁠35546017
Sep 15vs.South AlabamaW 31–⁠721409
Sep 22vs.The CitadelW 52–⁠14221013
Sep 29atMiamiL 37–⁠44228020
Oct 6vs.Florida StateW 17–⁠161202
Oct 20atMarylandW 20–⁠18322011
Oct 27atNorth CarolinaL 35–⁠43331014
Nov 3vs.VirginiaL 6–⁠331212
Nov 10vs.Wake ForestW 37–⁠6244030
Nov 17atClemsonL 48–⁠627105135
Nov 24vs.Boston CollegeW 27–⁠10318012
Dec 31 ✦vs.VanderbiltL 24–⁠38334015
2011 NC State 4 games, 9 catches, 84 yards, 1 TD
DateOpponentResultRecYdsTDLong
Sep 3vs.LibertyW 43–⁠212815
Oct 1vs.Georgia TechL 35–⁠45216012
Nov 12atBoston CollegeL 10–⁠14343023
Nov 26vs.MarylandW 56–⁠4121709
2010 NC State 2 games, 3 catches, 25 yards
DateOpponentResultRecYdsTDLong
Sep 4vs.Western CarolinaW 48–⁠7114014
Dec 28 ✦vs.West VirginiaW 23–⁠721108

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.