Quarterback, UTEP (from UCF, Incarnate Word), 2024–26
E.J. Colson
- Number
- No. 1
- Height
- 6′1″
- Weight
- 190 lb
- Class (2026)
- Sophomore
- Hometown
- Byron, GA
E.J. Colson plays quarterback for UTEP, after UCF (2024) and Incarnate Word (2025). Last time out, against San José State: 6 of 6, 87 yards; 8 carries, 15 yards. Colson leads UTEP in passing touchdowns and passing yards this season.
2026 so far
628 passing yards, 7 TD
Last game: 6 of 6, 87 yards; 8 carries, 15 yards vs. San José State, L 11–24
Next game: at North Dakota State, Oct 31
Filled bars: wins; outlined: losses.
Career highs
339passing yards, career highat UT Rio Grande Valley, 20254touchdown passes, career highvs. Texas Southern, 2026103rushing yards, career highvs. Abilene Christian, 20252rushing touchdowns, career highvs. Abilene Christian, 2025Passing
* The season in progress, so far.
| Season | Team | Cmp | Att | Pct | Yds | Y/A | TD | Int |
|---|---|---|---|---|---|---|---|---|
| 2024 | UCF | 9 | 16 | 56.3 | 64 | 4.0 | 1 | 1 |
| 2025 | Incarnate Word | 210 | 296 | 70.9 | 2,142 | 7.2 | 16 | 4 |
| 2026 | UTEP | 55 | 83 | 66.3 | 628 | 7.6 | 7 | 3 |
| Career | 274 | 395 | 69.4 | 2,834 | 7.2 | 24 | 8 | |
Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2024 | UCF | 13 | 14 | 1.1 | 0 | 9 |
| 2025 | Incarnate Word | 108 | 287 | 2.7 | 3 | 30 |
| 2026 | UTEP | 75 | 108 | 1.4 | 1 | 13 |
| Career | 196 | 409 | 2.1 | 4 | 30 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2024 | UCF | 1 | QB | Yr 1 | ||
| 2025 | Incarnate Word | 1 | QB | Yr 2 | ||
| 2026 | UTEP | 1 | QB | So. (Yr 3) | 6′1″ | 190 |
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 | Adj. pass | Adj. rush |
|---|---|---|---|---|---|---|---|---|---|
| 2024 | UCF | 29 | -0.25 | – | – | -7.3 | 20% | – | – |
| 2025 | Incarnate Word (FCS) | 405 | 0.24 | 49th (n=314) | 0.24 | 96.9 | 54% | – | – |
| 2026 | UTEP | 156 | -0.02 | 6th (n=273) | 0.21 | -2.6 | 43% | 0.14 | 0.10 |
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). Adjusted pass and rush: EPA per play adjusted for the defenses faced (CollegeFootballData’s WEPA). From CollegeFootballData, 2013 on.
Passing detail
| Season | Team | Success | Depth | After catch | Deep throws | Deep completed |
|---|---|---|---|---|---|---|
| 2026 | UTEP | 45% | 8.6 yds | 6.1 yds | 11 of 80 | 36% |
Success: passes that kept the offense on schedule. Depth: how far downfield his passes traveled in the air, on average. After catch: yards his receivers gained after the catch, per completion. Deep throws: the play-by-play gives depth and direction for about half of a passer’s throws; this is how many of those went deep, and how many of the deep ones were caught. From CollegeFootballData, FBS games, 2025 on.
Rushing detail
| Season | Team | Success | Line yards | Second level | Open field | Stuffed |
|---|---|---|---|---|---|---|
| 2026 | UTEP | 47% | 2.80 | 1.10 | 0.20 | 24% |
Where his yards came from, per carry: line yards are the ones credited to the blockers (the first few, and losses), second level the yards 5 to 10 past the line, open field those beyond 10. Success: carries that kept the offense on schedule. Stuffed: carries stopped at or behind the line. From CollegeFootballData, FBS games, 2025 on.
Game by game
2026 UTEP 6 games, 628 passing yards, 7 TD
| Date | Opponent | Result | Cmp | Att | Yds | TD | Int | Rush |
|---|---|---|---|---|---|---|---|---|
| Sep 4 | at | L 0–51 | 6 | 12 | 52 | 0 | 0 | 25 |
| Sep 12 | vs. | W 51–10 | 14 | 21 | 239 | 4 | 0 | 49 |
| Sep 19 | at | L 17–52 | 7 | 9 | 86 | 2 | 1 | −20 |
| Sep 26 | vs. | L 7–33 | 16 | 23 | 119 | 1 | 1 | 15 |
| Oct 3 | at | L 7–61 | 6 | 12 | 45 | 0 | 1 | 24 |
| Oct 17 | vs. | L 11–24 | 6 | 6 | 87 | 0 | 0 | 15 |
2025 Incarnate Word 10 games, 2,142 passing yards, 16 TD
| Date | Opponent | Result | Cmp | Att | Yds | TD | Int | Rush |
|---|---|---|---|---|---|---|---|---|
| Aug 23 | at | L 6–20 | 1 | 1 | 13 | 0 | 0 | 7 |
| Sep 13 | at | L 20–48 | 17 | 24 | 213 | 3 | 0 | 8 |
| Sep 20 | at | L 23–31 | 28 | 36 | 292 | 2 | 0 | 59 |
| Sep 27 | vs. | W 38–7 | 17 | 30 | 122 | 1 | 0 | 103 |
| Oct 4 | vs. | L 17–31 | 35 | 46 | 306 | 1 | 1 | −17 |
| Oct 18 | vs. | L 45–52 | 24 | 34 | 275 | 2 | 2 | 55 |
| Oct 25 | at | L 28–56 | 29 | 45 | 339 | 2 | 1 | 36 |
| Nov 1 | vs. | W 24–17 | 21 | 28 | 161 | 3 | 0 | 17 |
| Nov 8 | at | W 38–3 | 22 | 28 | 263 | 2 | 0 | −7 |
| Nov 15 | vs. | L 7–10 | 16 | 24 | 158 | 0 | 0 | 26 |
2024 UCF 2 games, 64 passing yards, 1 TD
| Date | Opponent | Result | Cmp | Att | Yds | TD | Int | Rush |
|---|---|---|---|---|---|---|---|---|
| Oct 12 | vs. | L 13–19 | 1 | 4 | −6 | 0 | 0 | 6 |
| Nov 29 | vs. | L 14–28 | 8 | 12 | 70 | 1 | 1 | 8 |
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.
