Linebacker, Texas State, 2016–19
Malik Alley
- Number
- No. 40
- Height
- 6′2″
- Weight
- 210 lb
- Class (2019)
- Senior
- Hometown
- Tyler, TX
Malik Alley played linebacker at Texas State (2016–19).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2017 | Texas State | 6 | 5 | 0 | 0 | 0 | 0 |
| 2018 | Texas State | 3 | 2 | 0.5 | 0 | 0 | 0 |
| 2019 | Texas State | 12 | 6 | 0 | 0 | 0 | 0 |
| Career | 21 | 13 | 0.5 | 0 | 0 | 0 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2016 | Texas State | 40 | LB | Fr. | ||
| 2017 | Texas State | 40 | LB | So. | ||
| 2018 | Texas State | 40 | LB | Jr. | ||
| 2019 | Texas State | 40 | LB | Sr. | 6′2″ | 210 |
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
2019 Texas State 4 games, 12 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Aug 29 | at Texas A&M | L 7–41 | 4 | 2 | 0 | 0 | 0 |
| Sep 14 | at SMU | L 17–47 | 3 | 2 | 0 | 0 | 0 |
| Sep 21 | vs. Georgia State | W 37–34 | 1 | 0 | 0 | 0 | 0 |
| Nov 16 | vs. Troy | L 27–63 | 4 | 2 | 0 | 0 | 0 |
2018 Texas State 2 games, 3 tackles
2017 Texas State 6 games, 6 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 23 | vs. UTSA | L 14–44 | 1 | 1 | 0 | 0 | 0 |
| Oct 7 | vs. UL Monroe | L 27–45 | 1 | 1 | 0 | 0 | 0 |
| Oct 28 | at Coastal Carolina | W 27–7 | 1 | 1 | 0 | 0 | 0 |
| Nov 11 | vs.Georgia State | L 30–33 | 1 | 1 | 0 | 0 | 0 |
| Nov 18 | at Arkansas State | L 12–30 | 1 | 0 | 0 | 0 | 0 |
| Nov 24 | atTroy | L 9–62 | 1 | 1 | 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.