Linebacker, Texas Tech (from Houston), 2012–⁠16

Luke Stice

Lettered 2012–⁠14 at Houston; 2016 at Texas Tech (school media guide)

Number
No. 37
Height
6′0″
Hometown
Midland, TX

Luke Stice played linebacker at Houston (2012–⁠15) and Texas Tech (2016).

Career highs

15tackles, career highvs. Baylor, 2016

Team titles: American champions, 2015

Defense

SeasonTeamTklSoloTFLSacksPDHur
2016Texas Tech51372100

Season lines from CollegeFootballData, regular season and bowls.

Defense before 2016

SeasonGSoloAstTkl
20124178
2013N135510
On file61218

Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources, marked by season: unmarked, cfbstats.com (Open Data Commons Attribution License), its game lines summed (G: the games he has a line in); N, 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
2012Houston37LB
2013Houston37LB
2014Houston37LB
2015Houston37LB
2016Texas Tech37LB6′0″

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 10 games, 51 tackles, 1 sack
DateOpponentResultTklSoloTFLSacksPD
Sep 3vs.Stephen F. AustinW 69–⁠1743000
Sep 10atArizona StateL 55–⁠6877000
Sep 17vs.Louisiana TechW 59–⁠4510000
Sep 29vs.KansasW 55–⁠1910000
Oct 8atKansas StateL 38–⁠4433000
Oct 29atTCUW 27–⁠2410000
Nov 5vs.TexasL 37–⁠4522000
Nov 12atOklahoma StateL 44–⁠4554210
Nov 19atIowa StateL 10–⁠66127000
Nov 25vs.BaylorW 54–⁠351511000
2013 Houston 2 games, 1 return, 4 yards
DateOpponentResultTklSoloTFLSacksPD
Sep 21vs.RiceW 31–⁠26–––––
Sep 28atUTSAW 59–⁠28–––––
2012 Houston 1 game, 1 return, 0 yards
DateOpponentResultTklSoloTFLSacksPD
Oct 18atSMUL 42–⁠72–––––

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.