Defensive back, Texas Tech, 2013–⁠16

Justis Nelson

Number
No. 31
Height
6′2″
Hometown
Mesquite, TX

Justis Nelson played defensive back at Texas Tech (2013–⁠16).

Career highs

10tackles, career highvs. Baylor, 2016

Defense

SeasonTeamTklSoloTFLSacksIntPDHur
2013Texas Tech––––1––
2015Texas Tech––––2––
2016Texas Tech59460.500121
Career59460.503121

Season lines from CollegeFootballData, regular season and bowls. A dash: the source has no number for that season (often an FCS season), and career totals count only the numbers on file.

Defense before 2016

SeasonGSoloAstTklIntPBU
20135921114

Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources: NCAA statistics, via octonion/football, the season’s official lines (G: games played). A dash: the source has no number for it.

On the roster

SeasonTeamNo.PosHt
2013Texas Tech31DB
2014Texas Tech31DB
2015Texas Tech31DB
2016Texas Tech31DB6′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 Texas Tech 12 games, 59 tackles
DateOpponentResultTklSoloTFLSacksIntPD
Sep 3vs.Stephen F. AustinW 69–⁠17550000
Sep 10atArizona StateL 55–⁠68650002
Sep 17vs.Louisiana TechW 59–⁠45320.5002
Sep 29vs.KansasW 55–⁠19320000
Oct 8atKansas StateL 38–⁠44110001
Oct 15vs.West VirginiaL 17–⁠48330001
Oct 22vs.OklahomaL 59–⁠66550000
Oct 29atTCUW 27–⁠24540003
Nov 5vs.TexasL 37–⁠45540002
Nov 12atOklahoma StateL 44–⁠45650000
Nov 19atIowa StateL 10–⁠66740000
Nov 25vs.BaylorW 54–⁠351060001
2015 Texas Tech 2 games, 2 INT
DateOpponentResultTklSoloTFLSacksIntPD
Oct 24atOklahomaL 27–⁠63––––1–
Nov 7atWest VirginiaL 26–⁠31––––1–
2013 Texas Tech 1 game, 1 INT
DateOpponentResultTklSoloTFLSacksIntPD
Dec 30 ✦vs.Arizona StateW 37–⁠23––––1–

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.