Defensive back, Colorado, 2015–18
Daniel Talley
- Number
- No. 28
- Height
- 6′2″
- Weight
- 215 lb
- Class (2018)
- Senior
- Hometown
- Aurora, CO
Daniel Talley played defensive back at Colorado (2015–18).
Defense
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2015 | Colorado | 28 | DB | Fr. | ||
| 2016 | Colorado | 28 | DB | So. | ||
| 2017 | Colorado | 28 | DB | Jr. | ||
| 2018 | Colorado | 28 | DB | Sr. | 6′2″ | 215 |
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 Colorado 7 games, 11 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Aug 31 | vs. Colorado State | W 45–13 | 1 | 0 | 0 | 0 | 0 |
| Sep 8 | at Nebraska | W 33–28 | 1 | 1 | 0 | 0 | 0 |
| Sep 15 | vs. New Hampshire | W 45–14 | 2 | 2 | 1 | 0 | 0 |
| Oct 13 | at USC | L 20–31 | 2 | 2 | 0 | 0 | 0 |
| Oct 27 | vs. Oregon State | L 34–41 | 1 | 1 | 0 | 0 | 0 |
| Nov 10 | vs. Washington State | L 7–31 | 2 | 2 | 0 | 0 | 0 |
| Nov 17 | vs. Utah | L 7–30 | 2 | 2 | 0 | 0 | 0 |
2017 Colorado 5 games, 5 tackles, 1 sack
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 9 | vs. Texas State | W 37–3 | 1 | 1 | 1 | 1 | 0 |
| Sep 23 | vs. Washington | L 10–37 | 1 | 1 | 0 | 0 | 0 |
| Oct 14 | atOregon State | W 36–33 | 1 | 1 | 0 | 0 | 0 |
| Oct 28 | vs. California | W 44–28 | 1 | 1 | 0 | 0 | 0 |
| Nov 11 | vs.USC | L 24–38 | 1 | 1 | 0 | 0 | 0 |
2016 Colorado 1 game, 1 tackle
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 17 | at Michigan | L 28–45 | 1 | 1 | 1 | 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.