Defensive back, Louisville, 2016–18
Lamarques Thomas
- Number
- No. 24
- Height
- 6′0″
- Weight
- 184 lb
- Class (2018)
- Junior
- Hometown
- Clinton, MS
Lamarques Thomas played defensive back at Louisville (2016–18).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2017 | Louisville | 8 | 6 | 0 | 0 | 0 | 0 |
| 2018 | Louisville | 7 | 4 | 0 | 0 | 0 | 0 |
| Career | 15 | 10 | 0 | 0 | 0 | 0 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2016 | Louisville | 24 | DB | Fr. | ||
| 2017 | Louisville | 24 | DB | So. | ||
| 2018 | Louisville | 24 | DB | Jr. | 6′0″ | 184 |
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 Louisville 5 games, 7 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 1 | vs. Alabama | L 14–51 | 1 | 1 | 0 | 0 | 0 |
| Sep 15 | vs. Western Kentucky | W 20–17 | 2 | 1 | 0 | 0 | 0 |
| Sep 22 | at Virginia | L 3–27 | 2 | 2 | 0 | 0 | 0 |
| Sep 29 | vs. Florida State | L 24–28 | 1 | 0 | 0 | 0 | 0 |
| Nov 24 | vs. Kentucky | L 10–56 | 1 | 0 | 0 | 0 | 0 |
2017 Louisville 7 games, 8 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 2 | vs. Purdue | W 35–28 | 1 | 1 | 0 | 0 | 0 |
| Sep 9 | at North Carolina | W 47–35 | 1 | 1 | 0 | 0 | 0 |
| Sep 16 | vs. Clemson | L 21–47 | 1 | 1 | 0 | 0 | 0 |
| Sep 23 | vs. Kent State | W 42–3 | 1 | 0 | 0 | 0 | 0 |
| Oct 5 | at NC State | L 25–39 | 1 | 0 | 0 | 0 | 0 |
| Oct 14 | vs. Boston College | L 42–45 | 2 | 2 | 0 | 0 | 0 |
| Dec 30 ✦ | vs. Mississippi State | L 27–31 | 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.