Safety, NC State, 2025–26
Tristan Teasdell
Lettered 2025 (school media guide)
- Number
- No. 3
- Height
- 5′11″
- Weight
- 180 lb
- Class (2026)
- Freshman
- Hometown
- Leesburg, VA
Tristan Teasdell plays safety for NC State. Last time out, against Louisville: 4 tackles.
2026 so far
17 tackles
Last game: 4 tackles vs. Louisville, W 31–28
Next game: at Stanford, Oct 23
Filled bars: wins; outlined: losses.
Defense
* The season in progress, so far.
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
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 NC State 5 games, 17 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Aug 29 | at Virginia | L 8–34 | 5 | 1 | 0 | 0 | 0 | 0 |
| Sep 11 | vs. Richmond | W 73–0 | 2 | 2 | 0 | 0 | 0 | 0 |
| Sep 19 | at Vanderbilt | L 31–35 | 3 | 2 | 0 | 0 | 0 | 0 |
| Sep 26 | vs. App State | W 41–31 | 3 | 0 | 0 | 0 | 0 | 0 |
| Oct 3 | vs. Louisville | W 31–28 | 4 | 0 | 0 | 0 | 0 | 0 |
2025 NC State 7 games, 23 tackles, 1 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Oct 4 | vs. Campbell | W 56–10 | 1 | 0 | 0 | 0 | 0 | 0 |
| Oct 25 | at Pittsburgh | L 34–53 | 4 | 0 | 0 | 0 | 1 | 0 |
| Nov 1 | vs. Georgia Tech | W 48–36 | 4 | 2 | 0 | 0 | 0 | 0 |
| Nov 15 | at Miami | L 7–41 | 2 | 1 | 0 | 0 | 0 | 0 |
| Nov 21 | vs. Florida State | W 21–11 | 6 | 3 | 0 | 0 | 0 | 0 |
| Nov 29 | vs. North Carolina | W 42–19 | 2 | 1 | 0 | 0 | 0 | 0 |
| Dec 19 ✦ | vs. Memphis | W 31–7 | 4 | 2 | 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.