Cornerback, Rice, 2025–26
Jerrick Harper
- Number
- No. 5
- Height
- 6′0″
- Weight
- 191 lb
- Class (2026)
- Senior
- Hometown
- Silsbee, TX
Jerrick Harper plays cornerback for Rice. Last time out, at East Carolina: 1 tackles.
2026 so far
5 tackles, 1 INT
Last game: 1 tackles at East Carolina, L 12–28
Next game: at Florida Atlantic, 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 Rice 5 games, 5 tackles, 1 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 5 | vs. Houston Christian | W 31–3 | – | – | – | – | 1 | – |
| Sep 12 | at Notre Dame | L 0–52 | 1 | 1 | 0 | 0 | 0 | 0 |
| Sep 26 | at Fresno State | L 24–38 | 1 | 1 | 0 | 0 | 0 | 0 |
| Oct 3 | vs. UTSA | L 14–16 | 2 | 2 | 0 | 0 | 0 | 0 |
| Oct 10 | at East Carolina | L 12–28 | 1 | 0 | 0 | 0 | 0 | 0 |
2025 Rice 8 games, 23 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Sep 6 | vs. Houston | L 9–35 | 1 | 0 | 0 | 0 | 0 | 0 |
| Sep 13 | vs. Prairie View A&M | W 38–17 | 2 | 1 | 0 | 0 | 0 | 0 |
| Sep 27 | at Navy | L 13–21 | 1 | 0 | 0 | 0 | 0 | 0 |
| Oct 4 | vs. Florida Atlantic | L 21–27 | 1 | 1 | 0 | 0 | 0 | 0 |
| Oct 11 | atUTSA | L 13–61 | 3 | 2 | 0 | 0 | 0 | 0 |
| Oct 25 | vs. UConn | W 37–34 | 6 | 3 | 0 | 0 | 0 | 1 |
| Nov 29 | at South Florida | L 3–52 | 5 | 0 | 0.5 | 0 | 0 | 1 |
| Jan 2 ✦ | vs. Texas State | L 10–41 | 4 | 2 | 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.