Usage Score
5.6
Player Dossier
2016-2019Baylor
WR • 6'2" • 211 lbs • Mckinney, TX, USA
Marques Jones reads as a vertical playmaker based on recent role and receiving efficiency.
Usage Score
5.6
Efficiency
100
Consistency
50
Season Value
41.3
Career Arc
Value trend by season
Best season by value score: 2018 Postseason · Baylor
Snapshot
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.
Marques Jones, WR. Best season Best season by value score: 2018 Postseason · Baylor. Marques Jones reads as a vertical playmaker based on recent role and receiving efficiency.
Marques Jones played WR for Baylor. Across 4 tracked seasons, Marques Jones recorded 301 receiving yards, 3 tackles, and 2 touchdowns. His top tracked season came in 2018 with Baylor.
Lead takeaway
Best season by value score: 2018 Postseason
Baylor paired 247 primary output with 64.7 efficiency.
Supporting note
2019 Regular Season role shape
target-driven usage with 100 efficiency.
Supporting note
Career value cooled off
2019 Regular Season fell back from the prior stop by season value score.
Supporting note
Peak game by takeover score: Kansas
Win with an explosive receiving profile. It landed in the 100th percentile of the selected season.
Analysis workspace
Filter the strongest season sample, inspect game-level shape, and then drop into the full log without losing the story of the year.
Understand the selected season before dropping into the full game log.
Games
2
Receiving Yards / G
9.5
Efficiency
100
Usage
5.6
Consistency
50
Best Game by takeover score
Kansas
Active game
Hover over a point
Hover or select a game to keep its context visible here without the page shifting around.
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. Oklahoma State: 0. Kansas: 19
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.
Compare how this player performed across different situations. "Games" shows how many matchups are included in each split.
Dense stat lines with inline explanations and season-linked highlights.
2 games
Featured metric
Receiving Yards
Top game by takeover score
Kansas
Best efficiency game
100 vs Kansas
Track team changes, role shifts, and season-to-season movement.
Baylor
2016-2019
Opening stop
Season Progression
| Season | Team | Primary | Efficiency | Usage | Delta |
|---|---|---|---|---|---|
| 2016 Regular Season | Baylor | 0 | — | — | — |
| 2017 Regular Season | Baylor | 35 | 78.4 | 7.2 | 35 |
| 2018 Postseason | Baylor | 247 | 64.7 | 8 | 212 |
| 2018 Regular Season | Baylor | 247 | 64.7 | 8 | 0 |
| 2019 Regular Season | Baylor | 19 | 100 | 5.6 | -228 |
#1 Featured game
Kansas
Win with an explosive receiving profile.
19
Primary metric
19 receiving yards with a 100 efficiency score.
#2
Vanderbilt
52
Primary metric
Win with an explosive receiving profile.
52 receiving yards with a 100 efficiency score.
#3
Texas
23
Primary metric
Loss with an explosive receiving profile.
23 receiving yards with a 76.7 efficiency score.
#4
Duke
38
Primary metric
Loss with an explosive receiving profile.
38 receiving yards with a 84.4 efficiency score.
#5
West Virginia
22
Primary metric
Loss with an explosive receiving profile.
22 receiving yards with a 100 efficiency score.
#1 Season by value score
2018 Postseason · Baylor
247 primary output · 64.7 efficiency · 8 usage
59.7
#2
2018 Regular Season · Baylor
59.7
247 primary · 64.7 efficiency · 8 usage
#3
2019 Regular Season · Baylor
41.3
19 primary · 100 efficiency · 5.6 usage
0
100+ receiving yards
0
8+ catch outings
0
2+ TD games
Recruit Profile
Class 2016 · Rating 0.78
Prestonwood Christian · Plano, TX
Career Facts
1
Career teams
5
Seasons tracked
301
Career Receiving Yards
Data Context
Coverage spans 5 tracked seasons, 18 games, and base opponent context only. Derived metrics fall back to raw production when share or rating context is missing.