Defensive back, Lamar, 2022–25
Kristian Pugh
- Number
- No. 1
- Height
- 5′11″
- Weight
- 182 lb
- Class (2025)
- Senior
- Hometown
- Beaumont, TX
Kristian Pugh played defensive back at Lamar (2022–25).
Career highs
10tackles, career highat Texas State, 2024Defense
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
2025 Lamar 4 games, 6 tackles, 3 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Aug 30 | at North Texas | L 0–51 | 6 | 4 | 0 | 0 | 0 | 0 |
| Sep 27 | vs. Central Arkansas | W 35–32 | – | – | – | – | 1 | – |
| Nov 15 | at Stephen F. Austin | L 15–26 | – | – | – | – | 1 | – |
| Nov 22 | vs. McNeese | L 19–21 | – | – | – | – | 1 | – |
No box score in the source for Sep 6 vs. South Dakota, so that game is not listed.
2024 Lamar 2 games, 10 tackles, 1 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Aug 31 | at Texas State | L 27–34 | 10 | 5 | 1 | 0 | 0 | 0 |
| Nov 2 | vs. SE Louisiana | L 27–30 | – | – | – | – | 1 | – |
2023 Lamar 2 games, 5 tackles, 1 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 9 | at UL Monroe | L 14–24 | 5 | 0 | 0 | 0 | 0 | 0 |
| Sep 16 | at South Dakota | L 6–35 | – | – | – | – | 1 | – |
2022 Lamar 3 games, 7 tackles, 1 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 10 | at SMU | L 16–45 | 6 | 6 | 1 | 0 | 0 | 1 |
| Sep 24 | at Northwestern State | L 27–35 | – | – | – | – | 1 | – |
| Nov 12 | at New Mexico State | L 14–51 | 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.