Safety, West Virginia, 2016–19
Deamonte Lindsay
- Number
- No. 26
- Height
- 6′1″
- Weight
- 208 lb
- Class (2019)
- Senior
- Hometown
- Martinsburg, WV
Deamonte Lindsay played safety at West Virginia (2016–19).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2018 | West Virginia | 10 | 8 | 0 | 0 | 1 | 0 |
| 2019 | West Virginia | 7 | 5 | 0 | 0 | 0 | 0 |
| Career | 17 | 13 | 0 | 0 | 1 | 0 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2016 | West Virginia | 26 | S | Fr. | ||
| 2017 | West Virginia | 26 | S | So. | ||
| 2018 | West Virginia | 26 | S | Jr. | ||
| 2019 | West Virginia | 26 | S | Sr. | 6′1″ | 208 |
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 West Virginia 4 games, 7 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Aug 31 | vs. James Madison | W 20–13 | 2 | 1 | 0 | 0 | 0 |
| Sep 7 | at Missouri | L 7–38 | 2 | 2 | 0 | 0 | 0 |
| Sep 14 | vs. NC State | W 44–27 | 2 | 1 | 0 | 0 | 0 |
| Sep 21 | at Kansas | W 29–24 | 1 | 1 | 0 | 0 | 0 |
2018 West Virginia 7 games, 10 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 1 | vs. Tennessee | W 40–14 | 1 | 1 | 0 | 0 | 0 |
| Sep 8 | vs. Youngstown State | W 52–17 | 3 | 2 | 0 | 0 | 0 |
| Sep 22 | vs. Kansas State | W 35–6 | 2 | 2 | 0 | 0 | 0 |
| Sep 29 | at Texas Tech | W 42–34 | 1 | 1 | 0 | 0 | 0 |
| Oct 6 | vs.Kansas | W 38–22 | 0 | 0 | 0 | 0 | 1 |
| Oct 25 | vs. Baylor | W 58–14 | 2 | 2 | 0 | 0 | 0 |
| Dec 28 ✦ | vs. Syracuse | L 18–34 | 1 | 0 | 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.