Cornerback, Coastal Carolina, 2017–18
Derambez Drinkard
- Number
- No. 36
- Height
- 5′11″
- Weight
- 165 lb
- Class (2018)
- Sophomore
- Hometown
- Blythewood, SC
Derambez Drinkard played cornerback at Coastal Carolina (2017–18).
Career highs
2interceptions, career highvs. App State, 2018Defense
| Season | Team | Tkl | Solo | TFL | Sacks | Int | PD | Hur |
|---|---|---|---|---|---|---|---|---|
| 2017 | Coastal Carolina | 2 | 2 | 0 | 0 | 0 | 0 | 0 |
| 2018 | Coastal Carolina | 5 | 4 | 0 | 0 | 2 | 0 | 0 |
| Career | 7 | 6 | 0 | 0 | 2 | 0 | 0 | |
Season lines from CollegeFootballData, regular season and bowls. A dash: the source has no number for that season (often an FCS season), and career totals count only the numbers on file.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2017 | Coastal Carolina | 36 | CB | Fr. | ||
| 2018 | Coastal Carolina | 36 | CB | So. | 5′11″ | 165 |
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 Coastal Carolina 4 games, 5 tackles, 2 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Oct 27 | at Georgia State | W 37–34 | 2 | 2 | 0 | 0 | 0 | 0 |
| Nov 3 | vs. App State | L 7–23 | 1 | 1 | 0 | 0 | 2 | 0 |
| Nov 10 | vs. Arkansas State | L 16–44 | 1 | 0 | 0 | 0 | 0 | 0 |
| Nov 23 | at South Alabama | L 28–31 | 1 | 1 | 0 | 0 | 0 | 0 |
2017 Coastal Carolina 3 games, 2 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 16 | at UAB | L 23–30 | – | – | – | – | – | – |
| Nov 11 | vs. Troy | L 17–42 | 1 | 1 | 0 | 0 | 0 | 0 |
| Dec 2 | vs. Georgia Southern | W 28–17 | 1 | 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.