Linebacker, Alabama A&M, 2017–18
Elijah Timarky
- Number
- No. 17
- Height
- 6′1″
- Weight
- 240 lb
- Hometown
- Chicago, IL
Elijah Timarky played linebacker at Alabama A&M (2017–18).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2017 | Alabama A&M | 6 | 3 | 0 | 0 | 0 | 0 |
| 2018 | Alabama A&M | 2 | 2 | 0 | 0 | 0 | 0 |
| Career | 8 | 5 | 0 | 0 | 0 | 0 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Ht | Wt |
|---|---|---|---|---|---|
| 2017 | Alabama A&M | 17 | LB | ||
| 2018 | Alabama A&M | 17 | LB | 6′1″ | 240 |
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
2018 Alabama A&M 1 game, 2 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 15 | at Cincinnati | L 7–63 | 2 | 2 | 0 | 0 | 0 |
No box score in the source for Sep 8 vs. North Alabama; Sep 22 vs. Southern; Sep 29 at Jackson State; Oct 6 at Texas Southern; Oct 13 vs. Alcorn State; Oct 27 vs. Alabama State; Nov 3 at Arkansas–Pine Bluff; Nov 10 vs. Grambling; Nov 17 at Mississippi Valley State, so those games are not listed.
2017 Alabama A&M 3 games, 6 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 2 | at UAB | L 7–38 | 1 | 1 | 0 | 0 | 0 |
| Sep 9 | at Vanderbilt | L 0–42 | 4 | 2 | 0 | 0 | 0 |
| Sep 16 | vs. South Alabama | L 0–45 | 1 | 0 | 0 | 0 | 0 |
No box score in the source for Sep 23 vs. Texas Southern; Sep 30 vs. Arkansas–Pine Bluff; Oct 7 at Southern; Oct 14 vs. Mississippi Valley State; Oct 28 at Alabama State; Nov 4 at Alcorn State; Nov 11 vs. Jackson State; Nov 18 vs. Kentucky State, so those games are not listed.
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.