Defensive end, North Texas, 2012–⁠16

Jarrian Roberts

Number
No. 30
Height
6′2″
Hometown
Clarksville, TX

Jarrian Roberts played defensive end at North Texas (2012–⁠16).

Defense

SeasonTeamTklSoloTFLSacksPDHur
2016North Texas17320.505

Season lines from CollegeFootballData, regular season and bowls.

Defense before 2016

SeasonGSoloAstTklTFLSacks
2013N103142.52
2014E9 of 1261016––
2015E12 of 1291423––

Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources, marked by season: N, NCAA statistics, via octonion/football, the season’s official lines (G: games played); E, ESPN play-by-play participants, via SportsDataverse: tackles only, counted in the games whose play-by-play names tacklers (G: those games, of his team’s), so part of the season, not its total. A dash: the source has no number for it.

On the roster

SeasonTeamNo.PosHt
2012North Texas30DE
2013North Texas30DE
2014North Texas30DE
2015North Texas30DE
2016North Texas30DE6′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.

Game by game

2016 North Texas 8 games, 17 tackles, 0.5 sacks
DateOpponentResultTklSoloTFLSacksPD
Sep 17atFloridaL 0–⁠3200000
Sep 24atRiceW 42–⁠3500000
Oct 1vs.Middle TennesseeL 13–⁠3050000
Oct 8vs.MarshallW 38–⁠212010.50
Oct 22atArmyW 35–⁠1821000
Oct 29atUTSAL 17–⁠3121100
Nov 5vs.Louisiana TechL 24–⁠4540000
Nov 19vs.Southern MissW 29–⁠2321000
2015 North Texas 2 games, 2 returns, 4 yards
DateOpponentResultTklSoloTFLSacksPD
Oct 10vs.Portland StateL 7–⁠66–––––
Nov 7atLouisiana TechL 13–⁠56–––––
2013 North Texas 2 games, 2 returns, 17 yards
DateOpponentResultTklSoloTFLSacksPD
Sep 7atOhioL 21–⁠27–––––
Nov 30atTulsaW 42–⁠10–––––

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.