Receiver, Colorado State (from Virginia Union, Wake Forest), 2024–26
Reginald Vick Jr
- Number
- No. 0
- Height
- 6′3″
- Weight
- 198 lb
- Class (2026)
- Senior
- Hometown
- Raleigh, NC
Reginald Vick Jr plays receiver for Colorado State, after Virginia Union (2024) and Wake Forest (2025). Last time out, against Oregon State: 5 catches, 99 yards. Vick leads Colorado State in receiving yards this season.
2026 so far
24 catches, 367 yards, 4 TD
Last game: 5 catches, 99 yards vs. Oregon State, L 26–56
Next game: vs. San Diego State, Oct 24
Filled bars: wins; outlined: losses.
Career highs
6catches, career highvs. Wyoming, 2026132receiving yards, career highat Hampton, 20243receiving touchdowns, career highvs. Wyoming, 2026Receiving
* The season in progress, so far.
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2024* | Virginia Union | 3 | 132 | 44.0 | 1 | 0 |
| 2026 | Colorado State | 24 | 367 | 15.3 | 4 | 57 |
| Career | 27 | 499 | 18.5 | 5 | 57 | |
Season lines from CollegeFootballData, regular season and bowls. * That team-season’s player lines are missing part of the team’s yards in our source, so these numbers may be short.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2024 | Virginia Union | 0 | WR | So. | ||
| 2025 | Wake Forest | 0 | WR | Jr. | ||
| 2026 | Colorado State | 0 | WR | Sr. | 6′3″ | 198 |
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 |
|---|---|---|---|---|---|---|---|
| 2024 | Virginia Union (II) | 1 | 4.46 | – | – | 4.5 | – |
| 2026 | Colorado State | 34 | 0.78 | 87th (n=829) | 0.43 | 26.4 | 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). From CollegeFootballData, 2013 on.
Game by game
2026 Colorado State 5 games, 24 catches, 367 yards, 4 TD
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Sep 5 | vs. Wyoming | W 35–13 | 6 | 75 | 3 | 57 | – |
| Sep 12 | vs. Southern Utah | W 58–24 | 3 | 33 | 0 | 19 | – |
| Sep 19 | vs. BYU | L 23–41 | 5 | 67 | 1 | 26 | – |
| Sep 26 | at UTSA | L 45–59 | 5 | 93 | 0 | 37 | 18 |
| Oct 3 | vs. Oregon State | L 26–56 | 5 | 99 | 0 | 50 | – |
2024 Virginia Union 1 game, 3 catches, 132 yards, 1 TD
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Sep 7 | at Hampton | L 21–33 | 3 | 132 | 1 | 0 | – |
No box score in the source for Aug 31 at Kentucky State; Sep 21 at Johnson C. Smith; Sep 28 vs. Shaw; Oct 5 vs. Winston-Salem State; Oct 12 vs. Elizabeth City State; Oct 19 at Lincoln (PA); Oct 26 at Bowie State; Nov 2 vs. Bluefield State; Nov 9 at Virginia State; Nov 16 at Virginia State; Nov 23 at Wingate; Nov 30 vs. Lenoir Rhyne; Dec 7 at Valdosta State, so those games are not listed.
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.