Cornerback, UTEP, 2020–23
Ilijah Johnson
- Number
- No. 32
- Height
- 5′11″
- Weight
- 170 lb
- Class (2023)
- Sophomore
- Hometown
- Maricopa, AZ
Ilijah Johnson played cornerback at UTEP (2020–23).
Defense
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
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2020 | UTEP | 32 | CB | Yr 1 | ||
| 2021 | UTEP | 32 | CB | Yr 2 | ||
| 2022 | UTEP | 32 | CB | Yr 3 | ||
| 2023 | UTEP | 32 | CB | So. (Yr 4) | 5′11″ | 170 |
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
2023 UTEP 3 games, 3 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Aug 26 | at Jacksonville State | L 14–17 | 0 | 0 | 0 | 0 | 0 | 1 |
| Sep 16 | at Arizona | L 10–31 | 2 | 2 | 0 | 0 | 0 | 0 |
| Sep 29 | vs. Louisiana Tech | L 10–24 | 1 | 0 | 0 | 0 | 0 | 0 |
2022 UTEP 8 games, 20 tackles, 2 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 3 | at Oklahoma | L 13–45 | 2 | 0 | 0 | 0 | 0 | 0 |
| Sep 10 | vs. New Mexico State | W 20–13 | 2 | 2 | 1 | 0 | 0 | 3 |
| Sep 17 | at New Mexico | L 10–27 | 3 | 1 | 0.5 | 0 | 0 | 0 |
| Sep 23 | vs. Boise State | W 27–10 | 0 | 0 | 0 | 0 | 0 | 3 |
| Oct 1 | at Charlotte | W 41–35 | 2 | 2 | 0 | 0 | 1 | 0 |
| Oct 8 | atLouisiana Tech | L 31–41 | 2 | 1 | 0 | 0 | 0 | 0 |
| Oct 29 | vs. Middle Tennessee | L 13–24 | 3 | 0 | 0 | 0 | 0 | 0 |
| Nov 3 | at Rice | L 30–37 | 6 | 5 | 0 | 0 | 1 | 0 |
2020 UTEP 2 games, 4 tackles
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.