Defensive back, Florida International (from Colgate, Texas Tech), 2019–22
Kyan Brumfield
Lettered 2020 at Texas Tech (school media guide)
- Number
- No. 28
- Height
- 6′0″
- Weight
- 185 lb
- Class (2022)
- Senior
- Hometown
- SAN ANTONIO, TX
Kyan Brumfield played defensive back at Colgate (2019), Texas Tech (2020) and Florida International (2022).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2019 | Colgate | 4 | 1 | 0 | 0 | 0 | 0 |
| 2022 | Florida International | 3 | 2 | 0 | 0 | 0 | 0 |
| Career | 7 | 3 | 0 | 0 | 0 | 0 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2019 | Colgate | 28 | DB | Fr. | ||
| 2020 | Texas Tech | 28 | DB | So. | ||
| 2022 | Florida International | 28 | DB | Sr. | 6′0″ | 185 |
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
2022 Florida International 3 games, 3 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 24 | at Western Kentucky | L 0–73 | 1 | 1 | 0 | 0 | 0 |
| Oct 22 | at Charlotte | W 34–15 | 1 | 0 | 0 | 0 | 0 |
| Nov 5 | at North Texas | L 14–52 | 1 | 1 | 0 | 0 | 0 |
2019 Colgate 1 game, 4 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Aug 31 | at Air Force | L 7–48 | 4 | 1 | 0 | 0 | 0 |
No box score in the source for Aug 24 vs. Villanova; Sep 14 at William & Mary; Sep 21 vs. Maine; Sep 28 at Dartmouth; Oct 5 vs. Lehigh; Oct 12 vs. Bucknell; Oct 19 at Cornell; Oct 26 at Holy Cross; Nov 2 at Georgetown; Nov 9 vs. Fordham; Nov 16 at Lafayette, 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.