Usage Score
9.1
Player Dossier
2016-2018Rutgers
Trey Sneed
RB • 5'11" • 215 lbs • Orange Park, FL, USA
Balanced backfield optionSteady chain mover
Trey Sneed leans balanced backfield option traits and 33.2 efficiency.
Efficiency
33.2
Consistency
48.4
Season Value
46.9
Career Arc
Value trend by season
Best season by value score: 2018 Regular Season · Rutgers
161718
Snapshot
- Career Teams
- 1
- Seasons Tracked
- 3
- Program Path
- Rutgers
- Peak Game
- Peak game by takeover score: Ohio
Scouting Read
Best season and peak-game context are pinned here so the rest of the page can stay analytical without losing the headline story.
Trey Sneed, RB. Best season Best season by value score: 2018 Regular Season · Rutgers. Trey Sneed leans balanced backfield option traits and 33.2 efficiency.
Player insights
Lead takeaway
Best season by value score: 2018 Regular Season
Rutgers paired 66 primary output with 33.2 efficiency.
Supporting note
2018 Regular Season role shape
backfield-heavy usage with 33.2 efficiency.
Supporting note
Career value is trending up
2018 Regular Season improved on the prior stop by season value score.
Supporting note
Peak game by takeover score: Ohio
Game with 104 yards from scrimmage and efficient touch value. It landed in the 100th percentile of the selected season.
Analysis workspace
Season Workbench
Filter the strongest season sample, inspect game-level shape, and then drop into the full log without losing the story of the year.
Season Explorer
Understand the selected season before dropping into the full game log.
2018 Regular Season · Rutgers
Games
4
Scrimmage Yards / G
16.5
Efficiency
33.2
Usage
9.1
Consistency
48.4
Best Game by takeover score
Ohio
Not enough games exist for the full explorer. The summary cards stay available so the season still reads clearly.
Game-by-Game Trend
Not enough games are available for a full trend line yet.
Volume vs Efficiency
Scatter view is hidden because this season does not have enough game-to-game variety yet.
Split Comparison
Game Log
Dense stat lines with inline explanations and season-linked highlights.
1 games
Featured metric
Scrimmage Yards
Top game by takeover score
Ohio
Best efficiency game
48.6 vs Ohio
| Result | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| Sat 9/24 | @ Ohio | — | 19 | 88 | 4.60 | 0 | 3 | 16 | 4.7 |
Career Arc
Track team changes, role shifts, and season-to-season movement.
- 1
Rutgers
2016-2018
Opening stop
Season Progression
201620172018
| Season | Team | Primary | Efficiency | Usage | Delta |
|---|---|---|---|---|---|
| 2016 Regular Season | Rutgers | 55 | 30.9 | 3.8 | — |
| 2017 Regular Season | Rutgers | 0 | — | — | -55 |
| 2018 Regular Season | Rutgers | 66 | 33.2 | 9.1 | 66 |
Signature Performances
Top Games
#1 Featured game
Ohio
Game with 104 yards from scrimmage and efficient touch value.
104
Primary metric
104 scrimmage yards and — usage.
#2
Ball State
27
Primary metric
Game with 27 yards from scrimmage and efficient touch value.
27 scrimmage yards and — usage.
#3
Michigan
27
Primary metric
Loss with 27 yards from scrimmage and efficient touch value.
27 scrimmage yards and 21.1 usage.
#4
Northwestern
36
Primary metric
Loss with 36 yards from scrimmage and efficient touch value.
36 scrimmage yards and 22 usage.
#5
Maryland
28
Primary metric
Loss with 28 yards from scrimmage and efficient touch value.
28 scrimmage yards and 12.8 usage.
Top Seasons
#1 Season by value score
2018 Regular Season · Rutgers
66 primary output · 33.2 efficiency · 9.1 usage
46.9
#2
2016 Regular Season · Rutgers
36
55 primary · 30.9 efficiency · 3.8 usage
#3
2017 Regular Season · Rutgers
—
0 primary · — efficiency · — usage
Milestones
1
100+ rush yards
0
150+ scrimmage yards
1
2+ TD games
Bio, Recruit, and Data Context
Recruit Profile
3★
Class 2023 · Rating 0.8539
Westlake · Austin, TX
- Committed To
- Kansas
- Commit Date
- Jan 1, 2023
Career Facts
1
Career teams
3
Seasons tracked
121
Career Scrimmage Yards
Data Context
Coverage spans 3 tracked seasons, 16 games, and base opponent context only. Derived metrics fall back to raw production when share or rating context is missing.