Linebacker, Elon, 2016–19
T.J. Speight
- Number
- No. 53
- Height
- 5′10″
- Weight
- 221 lb
- Hometown
- Chicago, IL
T.J. Speight played linebacker at Elon (2016–19).
Defense
Season lines from CollegeFootballData, regular season and bowls.
On the roster
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 Elon 1 game, 2 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 21 | at Wake Forest | L 7–49 | 2 | 0 | 0.5 | 0 | 0 |
No box score in the source for Aug 31 at North Carolina A&T; Sep 7 vs. The Citadel; Sep 14 at Richmond; Sep 28 vs. James Madison; Oct 5 at New Hampshire; Oct 12 vs. Delaware; Oct 26 at Rhode Island; Nov 2 vs. William & Mary; Nov 9 vs. Maine; Nov 23 at Towson, so those games are not listed.
2018 Elon 1 game, 3 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 1 | at South Florida | L 14–34 | 3 | 1 | 1 | 0 | 0 |
No box score in the source for Sep 8 vs. Furman; Sep 22 at Charleston Southern; Sep 29 vs. New Hampshire; Oct 6 at James Madison; Oct 13 at Delaware; Oct 20 vs. Richmond; Nov 3 vs. Rhode Island; Nov 10 vs. Towson; Nov 17 at Maine; Nov 24 at Wofford, so those games are not listed.
2017 Elon 1 game, 2 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Aug 31 | at Toledo | L 13–47 | 2 | 0 | 0 | 0 | 0 |
No box score in the source for Sep 9 at Furman; Sep 16 vs. Charleston Southern; Sep 23 at Richmond; Sep 30 vs. UAlbany; Oct 7 vs. William & Mary; Oct 21 at Rhode Island; Oct 28 at Villanova; Nov 4 vs. Towson; Nov 11 at New Hampshire; Nov 18 vs. James Madison; Nov 25 vs. Furman, 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.