Usage Score
20.6
Player Dossier
2018-2022Temple
Adonicas Sanders
WR • 6'1" • 190 lbs • North Charleston, SC, USA
Reliable chain-moverPossession profile
Adonicas Sanders reads as a reliable chain-mover based on recent role and receiving efficiency.
Efficiency
64.9
Consistency
68.7
Season Value
62.2
Career Arc
Value trend by season
Best season by value score: 2022 Regular Season · Temple
1819202122
Snapshot
- Career Teams
- 2
- Seasons Tracked
- 5
- Program Path
- Georgia Tech • Temple
- Peak Game
- Peak game by takeover score: NC State
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.
Adonicas Sanders, WR. Best season Best season by value score: 2022 Regular Season · Temple. Adonicas Sanders reads as a reliable chain-mover based on recent role and receiving efficiency.
Player insights
Lead takeaway
Best season by value score: 2022 Regular Season
Temple paired 437 primary output with 64.9 efficiency.
Supporting note
2022 Regular Season role shape
target-driven usage with 64.9 efficiency.
Supporting note
Career value is trending up
2022 Regular Season improved on the prior stop by season value score.
Supporting note
Multi-stop career journey
Production spans 2 team stops, with role shifts visible across Georgia Tech, Temple.
Supporting note
Peak game by takeover score: Massachusetts
Win with an explosive receiving profile. 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.
2022 Regular Season · Temple
Games
9
Receiving Yards / G
48.6
Efficiency
64.9
Usage
20.6
Consistency
68.7
Best Game by takeover score
Houston
Hover a point or expand a game row to keep the active game context visible here.
Active game
Hover over a point
Hover or select a game to keep its context visible here without the page shifting around.
Game-by-Game Trend
Follow how the selected stat changes from one game to the next. Spikes mark standout outings, while dips show quieter weeks.
Chronological game order.
Game by game trend chart. Duke: 39. Unknown: 6. Rutgers: 90. Massachusetts: 101. Memphis: 57. UCF: 57. Tulsa: 2. South Florida: 45. Houston: 40
Volume vs Efficiency
Each dot is a game. Farther right means the player carried more of the workload, and higher means they were more efficient with those chances.
Low volumeHigh quality
High volumeHigh quality
Low volumeLower quality
High volumeLower quality
Volume on the x-axis, quality on the y-axis.
Volume versus efficiency scatter chart. Duke: 4 by 65. Unknown: 1 by 40. Rutgers: 8 by 75. Massachusetts: 4 by 100. Memphis: 4 by 95. UCF: 7 by 54.3. Tulsa: 1 by 13.3. South Florida: 4 by 75. Houston: 4 by 66.7
Split Comparison
Compare how this player performed across different situations. "Games" shows how many matchups are included in each split.
Wins73 · Games = 2 · +25.5 vs Losses
Losses47.5 · Games = 6 · -25.5 vs Wins
First Half58.6 · Games = 5 · +22.6 vs Second Half
Second Half36 · Games = 4 · -22.6 vs First Half
Game Log
Dense stat lines with inline explanations and season-linked highlights.
9 games
Featured metric
Receiving Yards
Top game by takeover score
Massachusetts
Best efficiency game
100 vs Massachusetts
| Result | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| Sat 11/12 | @ Houston | L 36-43 | — | 4 | 40 | 10 | 10 | 0 | 16 |
| Sat 11/5 | vs South Florida | W 54-28 | — | 4 | 45 | 11.3 | 11.30 | 1 | 18 |
| Fri 10/21 | vs Tulsa | L 16-27 | — | 1 | 2 | 2 | 2 | 0 | 2 |
| Thu 10/13 | @ UCF | L 13-70 | — | 7 | 57 | 8.1 | 8.10 | 0 | 15 |
| Sat 10/1 | @ Memphis | L 3-24 | — | 4 | 57 | 12 | 14.30 | 0 | 30 |
| Sat 9/24 | vs Massachusetts100 receiving yards | W 28-0 | — | 4 | 101 | 25.3 | 25.30 | 1 | 50 |
| Sat 9/17 | vs RutgersHigh volume | L 14-16 | — | 8 | 90 | 9.5 | 11.30 | 0 | 23 |
| Sat 9/10 | vs Unknown | — | — | 1 | 6 | 5 | 6 | 0 | 6 |
| Fri 9/2 | @ Duke | L 0-30 | — | 4 | 39 | 8.8 | 9.80 | 0 | 11 |
Career Arc
Track team changes, role shifts, and season-to-season movement.
- 1
Georgia Tech
2018-2021
Opening stop
- 2
Temple
2022
Final stop
Season Progression
20182019202020212022
| Season | Team | Primary | Efficiency | Usage | Delta |
|---|---|---|---|---|---|
| 2018 Regular Season | Georgia Tech | 0 | — | — | — |
| 2019 Regular Season | Georgia Tech | 249 | 75.6 | 19.1 | 249 |
| 2020 Regular Season | Georgia Tech | 223 | 70.8 | 14.6 | -26 |
| 2021 Regular Season | Georgia Tech | 362 | 68.3 | 17.5 | 139 |
| 2022 Regular Season | Temple | 437 | 64.9 | 20.6 | 75 |
Signature Performances
Top Games
#1 Featured game
NC State
Loss with an explosive receiving profile.
105
Primary metric
105 receiving yards with a 100 efficiency score.
#2
Massachusetts
101
Primary metric
Win with an explosive receiving profile.
101 receiving yards with a 100 efficiency score.
#3
North Carolina
67
Primary metric
Loss with an explosive receiving profile.
67 receiving yards with a 100 efficiency score.
#4
Duke
69
Primary metric
Loss with an explosive receiving profile.
69 receiving yards with a 100 efficiency score.
#5
Virginia
79
Primary metric
Loss with an explosive receiving profile.
79 receiving yards with a 87.8 efficiency score.
Top Seasons
#1 Season by value score
2022 Regular Season · Temple
437 primary output · 64.9 efficiency · 20.6 usage
62.2
#2
2021 Regular Season · Georgia Tech
55.7
362 primary · 68.3 efficiency · 17.5 usage
#3
2019 Regular Season · Georgia Tech
48.4
249 primary · 75.6 efficiency · 19.1 usage
Milestones
2
100+ receiving yards
1
8+ catch outings
0
2+ TD games
Bio, Recruit, and Data Context
Recruit Profile
2★
Class 2017 · Rating 0.7911
Fort Dorchester · North Charleston, SC
- Committed To
- Georgia Tech
- Commit Date
- Jan 1, 2017
Career Facts
2
Career teams
5
Seasons tracked
1,271
Career Receiving Yards
Data Context
Coverage spans 5 tracked seasons, 34 games, and base opponent context only. Derived metrics fall back to raw production when share or rating context is missing.