Defensive back, SE Louisiana, 2018–19
Tre’ Spann
- Number
- No. 5
- Height
- 6′1″
- Weight
- 200 lb
- Hometown
- Southaven, MS
Tre’ Spann played defensive back at SE Louisiana (2018–19).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2018 | SE Louisiana | 3 | 0 | 0 | 0 | 0 | 0 |
| 2019 | SE Louisiana | 6 | 4 | 0.5 | 0 | 0 | 0 |
| Career | 9 | 4 | 0.5 | 0 | 0 | 0 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Ht | Wt |
|---|---|---|---|---|---|
| 2018 | SE Louisiana | 5 | DB | ||
| 2019 | SE Louisiana | 5 | DB | 6′1″ | 200 |
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 SE Louisiana 1 game, 6 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 14 | at Ole Miss | L 29–40 | 6 | 4 | 0.5 | 0 | 0 |
No box score in the source for Aug 30 vs. Jacksonville State; Sep 22 vs. Lamar; Sep 28 at Northwestern State; Oct 5 at McNeese; Oct 12 vs. Incarnate Word; Oct 26 at Houston Christian; Nov 2 vs. Stephen F. Austin; Nov 9 at Central Arkansas; Nov 16 at Abilene Christian; Nov 22 vs. Nicholls; Nov 30 vs. Villanova; Dec 7 at Montana, so those games are not listed.
2018 SE Louisiana 1 game, 3 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Aug 30 | at UL Monroe | L 31–34 | 3 | 0 | 0 | 0 | 0 |
No box score in the source for Sep 16 vs. Central Arkansas; Sep 22 at Lamar; Sep 30 vs. Northwestern State; Oct 6 at Incarnate Word; Oct 13 vs. Houston Christian; Oct 21 vs. Abilene Christian; Oct 27 at Sam Houston; Nov 3 vs. McNeese; Nov 16 at Nicholls, 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.