Quarterback, Western Carolina (from NC State), 2023–26
Lex Thomas
- Number
- No. 2
- Height
- 5′11″
- Weight
- 205 lb
- Class (2026)
- Junior
- Hometown
- Wake Forest, NC
Lex Thomas plays quarterback for Western Carolina, after NC State (2023–25). Last time out, at Mercer: 19 of 35, 215 yards, 1 TD, 1 INT; 15 carries, 18 yards. Thomas leads Western Carolina in passing touchdowns and passing yards this season.
2026 so far
1,693 passing yards, 8 TD
Last game: 19 of 35, 215 yards, 1 TD, 1 INT; 15 carries, 18 yards at Mercer, L 14–17
Next game: vs. Chattanooga, Oct 24
Filled bars: wins; outlined: losses.
Career highs
326passing yards, career highat Campbell, 20263touchdown passes, career highvs. Eastern Kentucky, 202694rushing yards, career highvs. Tennessee Tech, 20263rushing touchdowns, career highat East Tennessee State, 2026Passing
* The season in progress, so far.
| Season | Team | Cmp | Att | Pct | Yds | Y/A | TD | Int |
|---|---|---|---|---|---|---|---|---|
| 2024 | NC State | 5 | 8 | 62.5 | 65 | 8.1 | 1 | 1 |
| 2025 | NC State | 2 | 7 | 28.6 | 18 | 2.6 | 0 | 0 |
| 2026 | Western Carolina | 153 | 241 | 63.5 | 1,693 | 7.0 | 8 | 1 |
| Career | 160 | 256 | 62.5 | 1,776 | 6.9 | 9 | 2 | |
Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2024 | NC State | 1 | 9 | 9.0 | 0 | 9 |
| 2026 | Western Carolina | 81 | 274 | 3.4 | 5 | 39 |
| Career | 82 | 283 | 3.5 | 5 | 39 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2023 | NC State | 2 | QB | RS | ||
| 2024 | NC State | 2 | QB | Fr. | ||
| 2025 | NC State | 2 | QB | So. | ||
| 2026 | Western Carolina | 2 | QB | Jr. | 5′11″ | 205 |
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.
Per play
| Season | Team | Plays | EPA/play | Pctile | Median | Total | Usage |
|---|---|---|---|---|---|---|---|
| 2024 | NC State | 9 | 0.21 | – | – | 1.9 | – |
| 2025 | NC State | 7 | -0.27 | – | – | -1.9 | – |
| 2026 | Western Carolina (FCS) | 321 | 0.29 | 68th (n=273) | 0.21 | 94.7 | 60% |
Expected points added: how much the player’s plays moved the team’s expected score, per play and in total. Plays: total EPA divided by EPA per play, the plays the source credits to him (for a receiver roughly his catches and runs, not every target; for a passer, not every attempt), so it can differ from attempts plus carries. Percentile: against the position’s regulars that season across all divisions on file (quarterbacks with 150+ plays, backs 60+, receivers and tight ends 30+), with how many there were (n) and their median; a dash means too few plays to rank. A season in progress uses the full-season bar scaled by games played, never below 75 plays for quarterbacks, 30 for backs and 20 for receivers. The cohort grows or shrinks with the source’s coverage each season (2025 lists far more players), so compare percentiles rather than raw EPA across years. FCS seasons are marked. Usage: the share of the team’s plays the player was part of (shown from 20 plays). From CollegeFootballData, 2013 on.
Game by game
2026 Western Carolina 7 games, 1,693 passing yards, 8 TD
| Date | Opponent | Result | Cmp | Att | Yds | TD | Int | Rush |
|---|---|---|---|---|---|---|---|---|
| Aug 29 | vs. | W 45–21 | 27 | 35 | 320 | 3 | 0 | 69 |
| Sep 6 | at | L 19–28 | 25 | 44 | 326 | 2 | 0 | −11 |
| Sep 12 | at | L 10–62 | 23 | 32 | 165 | 0 | 0 | 18 |
| Sep 19 | vs. | W 58–14 | 24 | 33 | 268 | 1 | 0 | 34 |
| Sep 26 | at | L 31–58 | 16 | 32 | 163 | 0 | 0 | 52 |
| Oct 3 | vs. | W 44–20 | 19 | 30 | 236 | 1 | 0 | 94 |
| Oct 10 | at | L 14–17 | 19 | 35 | 215 | 1 | 1 | 18 |
2025 NC State 2 games, 18 passing yards
2024 NC State 2 games, 65 passing yards, 1 TD
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.
