Defensive back, Colorado, 2024–26
R.J. Johnson
- Number
- No. 5
- Height
- 6′2″
- Weight
- 185 lb
- Class (2026)
- Senior
- Hometown
- Mcdonough, GA
R.J. Johnson plays defensive back for Colorado. Last time out, against Utah: 5 tackles.
2026 so far
9 tackles
Last game: 5 tackles vs. Utah, L 24–27
Next game: at Oklahoma State, Oct 24
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 Colorado 3 games, 9 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 12 | vs. Weber State | W 52–21 | 2 | 1 | 0 | 0 | 0 | 1 |
| Oct 3 | vs. Texas Tech | L 7–29 | 2 | 2 | 0 | 0 | 0 | 2 |
| Oct 17 | vs. Utah | L 24–27 | 5 | 4 | 0 | 0 | 0 | 2 |
2025 Colorado 3 games, 7 tackles, 1 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Aug 29 | vs. Georgia Tech | L 20–27 | 3 | 2 | 0 | 0 | 0 | 0 |
| Sep 6 | vs. Delaware | W 31–7 | 3 | 3 | 0 | 0 | 1 | 1 |
| Sep 12 | at Houston | L 20–36 | 1 | 1 | 0 | 0 | 0 | 0 |
2024 Colorado 5 games, 7 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 21 | vs. Baylor | W 38–31 | 2 | 1 | 0 | 0 | 0 | 0 |
| Sep 28 | at UCF | W 48–21 | 1 | 1 | 0 | 0 | 0 | 0 |
| Oct 19 | at Arizona | W 34–7 | 2 | 1 | 0 | 0 | 0 | 0 |
| Nov 9 | atTexas Tech | W 41–27 | 1 | 0 | 0 | 0 | 0 | 0 |
| Nov 16 | vs.Utah | W 49–24 | 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.