Linebacker, Texas Tech, 2013–16
Malik Jenkins
- Number
- No. 41
- Height
- 6′1″
- Hometown
- Ennis, TX
Malik Jenkins played linebacker at Texas Tech (2013–16).
Career highs
14tackles, career hightwice; last at TCU, 2016Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2016 | Texas Tech | 75 | 53 | 2.5 | 0 | 2 | 2 |
Season lines from CollegeFootballData, regular season and bowls.
Defense before 2016
| Season | G | Solo | Ast | Tkl | TFL | Sacks | PBU |
|---|---|---|---|---|---|---|---|
| 2013 | 12 | 7 | 2 | 9 | 2 | 1 | 1 |
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
| Season | Team | No. | Pos | Ht |
|---|---|---|---|---|
| 2013 | Texas Tech | 41 | LB | |
| 2014 | Texas Tech | 41 | LB | |
| 2015 | Texas Tech | 41 | LB | |
| 2016 | Texas Tech | 41 | LB | 6′1″ |
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 11 games, 75 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 3 | vs. | W 69–17 | 5 | 3 | 0 | 0 | 0 |
| Sep 10 | at | L 55–68 | 8 | 7 | 0 | 0 | 0 |
| Sep 17 | vs. | W 59–45 | 5 | 3 | 0 | 0 | 0 |
| Oct 8 | at | L 38–44 | 3 | 3 | 0 | 0 | 0 |
| Oct 15 | vs. | L 17–48 | 2 | 0 | 0.5 | 0 | 0 |
| Oct 22 | vs. | L 59–66 | 14 | 11 | 2 | 0 | 0 |
| Oct 29 | at | W 27–24 | 14 | 10 | 0 | 0 | 1 |
| Nov 5 | vs. | L 37–45 | 8 | 5 | 0 | 0 | 0 |
| Nov 12 | at | L 44–45 | 6 | 4 | 0 | 0 | 1 |
| Nov 19 | at | L 10–66 | 4 | 2 | 0 | 0 | 0 |
| Nov 25 | vs. | W 54–35 | 6 | 5 | 0 | 0 | 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.
