Defensive back, UConn (from Toledo), 2024–26
Tyler McKinstry
- Number
- No. 7
- Height
- 5′9″
- Weight
- 182 lb
- Class (2026)
- Sophomore
- Hometown
- Atlanta, GA
Tyler McKinstry plays defensive back for UConn, after Toledo (2024–25). Last time out, against Syracuse: 4 tackles.
2026 so far
10 tackles
Last game: 4 tackles vs. Syracuse, L 41–42
Next game: vs. Massachusetts, Oct 23
Filled bars: wins; outlined: losses.
Defense
* The season in progress, so far.
Season lines from CollegeFootballData, regular season and bowls.
On the roster
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
2026 UConn 5 games, 10 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 5 | vs. Lafayette | W 56–7 | 1 | 1 | 0 | 0 | 1 |
| Sep 12 | vs. Maryland | L 14–38 | 2 | 1 | 0 | 0 | 0 |
| Sep 19 | at Southern Miss | W 48–20 | 1 | 1 | 1 | 0 | 1 |
| Sep 26 | at Miami (OH) | L 21–24 | 2 | 2 | 0 | 0 | 0 |
| Oct 3 | vs. Syracuse | L 41–42 | 4 | 2 | 0 | 0 | 0 |
2025 Toledo 4 games, 4 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 6 | vs. Western Kentucky | W 45–21 | 1 | 0 | 0 | 0 | 0 |
| Sep 13 | vs. Morgan State | W 60–0 | 1 | 0 | 0 | 0 | 0 |
| Sep 27 | vs. Akron | W 45–3 | 1 | 1 | 0 | 0 | 0 |
| Nov 22 | vs. Ball State | W 38–9 | 1 | 1 | 0 | 0 | 0 |
2024 Toledo 4 games, 4 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 14 | at Mississippi State | W 41–17 | 1 | 0 | 0.5 | 0 | 0 |
| Oct 26 | vs. Bowling Green | L 26–41 | 1 | 0 | 0 | 0 | 0 |
| Nov 12 | vs. Central Michigan | W 37–10 | 1 | 1 | 0 | 0 | 0 |
| Nov 26 | atAkron | L 14–21 | 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.