Running back, Arkansas–Pine Bluff (from Tennessee Tech), 2022–24
O.J. Ross
- Number
- No. 10
- Height
- 5′10″
- Weight
- 170 lb
- Class (2024)
- Freshman
- Hometown
- Cocoa, FL
O.J. Ross played running back at Tennessee Tech (2022–23) and Arkansas–Pine Bluff (2024).
Career highs
100rushing yards, career highvs. Arkansas Baptist, 20243rushing touchdowns, career highvs. Arkansas Baptist, 2024Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2022 | Tennessee Tech | 19 | 113 | 5.9 | 2 | 33 |
| 2023 | Tennessee Tech | 29 | 145 | 5.0 | 0 | 64 |
| 2024 | Arkansas–Pine Bluff | 21 | 150 | 7.1 | 4 | 54 |
| Career | 69 | 408 | 5.9 | 6 | 64 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2022 | Tennessee Tech | 10 | RB | Yr 1 | ||
| 2023 | Tennessee Tech | 10 | RB | Yr 2 | ||
| 2024 | Arkansas–Pine Bluff | 10 | RB | Fr. (Yr 3) | 5′10″ | 170 |
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 |
|---|---|---|---|---|---|---|---|
| 2022 | Tennessee Tech (FCS) | 26 | 0.57 | – | – | 14.9 | 7% |
| 2023 | Tennessee Tech (FCS) | 30 | 0.18 | – | – | 5.3 | 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
2024 Arkansas–Pine Bluff 3 games, 150 rushing yards, 4 TD
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Aug 29 | vs. Arkansas | L 0–70 | 5 | 13 | 0 | 5 | – | – |
| Sep 7 | vs.Arkansas Baptist | W 73–0 | 5 | 100 | 3 | 54 | – | – |
| Sep 14 | vs. Tennessee State | L 28–41 | 11 | 37 | 1 | 18 | – | – |
2023 Tennessee Tech 4 games, 145 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Oct 28 | at Robert Morris | W 38–13 | 7 | 29 | 0 | 18 | – | – |
| Nov 4 | vs. UT Martin | L 41–44 | 8 | 18 | 0 | 4 | – | – |
| Nov 11 | vs. Gardner-Webb | L 0–35 | 6 | 13 | 0 | 10 | 1 | 23 |
| Nov 18 | atTennessee State | W 35–0 | 8 | 85 | 0 | 64 | – | – |
2022 Tennessee Tech 6 games, 113 rushing yards, 2 TD
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 2 | at Kansas | L 10–56 | 2 | 5 | 0 | 5 | 1 | 21 |
| Oct 1 | atUT Martin | L 28–45 | 5 | 50 | 0 | 33 | – | – |
| Oct 29 | at Eastern Illinois | W 20–17 | – | – | – | – | 2 | 15 |
| Nov 5 | vs. Lindenwood | W 35–34 | 4 | 37 | 1 | 13 | 3 | 65 |
| Nov 12 | at North Alabama | W 35–27 | 4 | 14 | 1 | 7 | – | – |
| Nov 19 | vs. North Carolina Central | L 20–22 | 4 | 7 | 0 | 7 | 1 | 11 |
No box score in the source for Sep 17 vs. Samford, so that game is 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.