Receiver, Chattanooga (from Northern Colorado), 2023–25
Jamarii Robinson
- Number
- No. 8
- Height
- 6′2″
- Weight
- 179 lb
- Class (2025)
- Senior
- Hometown
- Randolph, MA
Jamarii Robinson played receiver at Northern Colorado (2023) and Chattanooga (2025).
Career highs
8catches, career highvs. Portland State, 202396receiving yards, career highvs. Portland State, 20232receiving touchdowns, career highvs. East Tennessee State, 2025Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2023 | Northern Colorado | 41 | 474 | 11.6 | 1 | 48 |
| 2025 | Chattanooga | 18 | 278 | 15.4 | 4 | 45 |
| Career | 59 | 752 | 12.7 | 5 | 48 | |
Returns
| Season | Team | KR | Yds | TD |
|---|---|---|---|---|
| 2023 | Northern Colorado | 6 | 126 | 0 |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2023 | Northern Colorado | 8 | WR | So. | ||
| 2025 | Chattanooga | 8 | WR | Sr. | 6′2″ | 179 |
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 |
|---|---|---|---|---|---|---|---|
| 2025 | Chattanooga (FCS) | 25 | 1.16 | – | – | 28.9 | 6% |
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
2025 Chattanooga 8 games, 18 catches, 278 yards, 4 TD
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Aug 30 | at Memphis | L 10–45 | 1 | 5 | 0 | 5 | – |
| Sep 6 | at Tennessee Tech | L 17–45 | 1 | 11 | 0 | 11 | – |
| Sep 13 | vs. Stetson | W 63–0 | 2 | 41 | 1 | 25 | – |
| Sep 27 | vs. The Citadel | L 10–28 | 5 | 89 | 0 | 45 | – |
| Oct 4 | at VMI | W 21–14 | 4 | 50 | 0 | 18 | – |
| Oct 18 | vs. East Tennessee State | W 42–38 | 2 | 24 | 2 | 20 | – |
| Oct 25 | at Samford | W 49–13 | 2 | 47 | 1 | 42 | – |
| Nov 1 | vs. Western Carolina | L 28–35 | 1 | 11 | 0 | 11 | – |
2023 Northern Colorado 11 games, 41 catches, 474 yards, 1 TD
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Aug 31 | at Abilene Christian | L 11–31 | – | – | – | – | 0 |
| Sep 9 | vs. Incarnate Word | L 7–42 | 3 | 28 | 0 | 12 | – |
| Sep 16 | at Washington State | L 21–64 | 4 | 39 | 1 | 18 | – |
| Sep 23 | at Idaho State | L 21–35 | 1 | 4 | 0 | 4 | – |
| Sep 30 | vs. Weber State | L 21–28 | 7 | 73 | 0 | 16 | – |
| Oct 14 | vs. Sacramento State | L 13–21 | 2 | 57 | 0 | 48 | −2 |
| Oct 21 | at Cal Poly | L 17–24 | 1 | 28 | 0 | 28 | – |
| Oct 28 | at Montana | L 0–40 | 2 | 40 | 0 | 33 | – |
| Nov 4 | vs. Idaho | L 13–27 | 6 | 37 | 0 | 13 | 7 |
| Nov 11 | at Northern Arizona | L 7–28 | 7 | 72 | 0 | 18 | – |
| Nov 18 | vs. Portland State | L 23–27 | 8 | 96 | 0 | 31 | 20 |
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.