Safety, UTEP (from USC), 2015–19
Ykili Ross
Lettered 2016–17 at USC (school media guide)
- Number
- No. 43
- Height
- 6′1″
- Weight
- 190 lb
- Class (2019)
- Senior
- Hometown
- Riverside, CA
Ykili Ross played safety at USC (2015–17) and UTEP (2019).
Team titles: Pac-12 champions, 2017
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
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
2019 UTEP 7 games, 20 tackles, 2 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Aug 31 | vs. Houston Christian | W 36–34 | 1 | 1 | 0 | 0 | 0 | 0 |
| Sep 7 | at Texas Tech | L 3–38 | 2 | 0 | 0 | 0 | 1 | 0 |
| Sep 21 | vs. Nevada | L 21–37 | 4 | 2 | 0 | 0 | 1 | 0 |
| Oct 19 | at Florida International | L 17–32 | 3 | 1 | 0 | 0 | 0 | 0 |
| Oct 26 | vs. Louisiana Tech | L 21–42 | 1 | 0 | 0 | 0 | 0 | 0 |
| Nov 2 | at North Texas | L 26–52 | 4 | 2 | 0 | 0 | 0 | 0 |
| Nov 30 | vs. Rice | L 16–30 | 5 | 4 | 0 | 0 | 0 | 0 |
2017 USC 7 games, 13 tackles, 2 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 9 | vs. Stanford | W 42–24 | 1 | 1 | 0 | 0 | 0 | 0 |
| Sep 23 | at California | W 30–20 | 2 | 1 | 0 | 0 | 1 | 0 |
| Sep 29 | at Washington State | L 27–30 | 1 | 0 | 0 | 0 | 0 | 0 |
| Oct 7 | vs. Oregon State | W 38–10 | 3 | 3 | 0 | 0 | 0 | 0 |
| Oct 14 | vs. Utah | W 28–27 | 5 | 2 | 1 | 0 | 0 | 0 |
| Oct 28 | at Arizona State | W 48–17 | 0 | 0 | 0 | 0 | 1 | 0 |
| Nov 18 | vs. UCLA | W 28–23 | 1 | 0 | 0 | 0 | 0 | 0 |
2016 USC 2 games, 2 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.