Usage Score
4.4
Player Dossier
2005-2009UCLA
WR • 6'5" • Oak Park, CA, USA
Gavin Ketchum reads as a reliable chain-mover based on recent role and receiving efficiency.
Usage Score
4.4
Efficiency
63.4
Consistency
63.3
Season Value
36
Career Arc
Value trend by season
Best season by value score: 2005 Regular Season · UCLA
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.
Gavin Ketchum, WR. Best season Best season by value score: 2005 Regular Season · UCLA. Gavin Ketchum reads as a reliable chain-mover based on recent role and receiving efficiency.
Gavin Ketchum played WR for UCLA. Across 5 tracked seasons, Gavin Ketchum recorded 342 receiving yards and 2 touchdowns. His top tracked season came in 2005 with UCLA.
Lead takeaway
Best season by value score: 2005 Regular Season
UCLA paired 153 primary output with 65.4 efficiency.
Supporting note
2009 Regular Season role shape
target-driven usage with 63.4 efficiency.
Supporting note
Career value cooled off
2009 Regular Season fell back from the prior stop by season value score.
Supporting note
Peak game by takeover score: Washington
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
10
Efficiency
63.4
Usage
4.4
Consistency
63.3
Best Game by takeover score
Washington
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. Oregon State: 4. Washington: 16
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
Washington
Best efficiency game
100 vs Washington
Track team changes, role shifts, and season-to-season movement.
UCLA
2005-2009
Opening stop
Season Progression
| Season | Team | Primary | Efficiency | Usage | Delta |
|---|---|---|---|---|---|
| 2005 Regular Season | UCLA | 153 | 65.4 | 6.6 | — |
| 2006 Postseason | UCLA | 57 | 68 | 6.3 | -96 |
| 2006 Regular Season | UCLA | 57 | 68 | 6.3 | 0 |
| 2007 Regular Season | UCLA | 51 | 61.1 | 10.9 | -6 |
| 2008 Regular Season | UCLA | 61 | 65 | 8.1 | 10 |
| 2009 Regular Season | UCLA | 20 | 63.4 | 4.4 | -41 |
#1 Featured game
Arizona State
Win with an explosive receiving profile.
80
Primary metric
80 receiving yards with a 100 efficiency score.
#2
Washington
32
Primary metric
Win with an explosive receiving profile.
32 receiving yards with a 100 efficiency score.
#3
Oregon State
21
Primary metric
Win with an explosive receiving profile.
21 receiving yards with a 100 efficiency score.
#4
Washington
16
Primary metric
Win with an explosive receiving profile.
16 receiving yards with a 100 efficiency score.
#5
Washington
24
Primary metric
Win with an explosive receiving profile.
24 receiving yards with a 80 efficiency score.
#1 Season by value score
2005 Regular Season · UCLA
153 primary output · 65.4 efficiency · 6.6 usage
49.3
#2
2008 Regular Season · UCLA
44.9
61 primary · 65 efficiency · 8.1 usage
#3
2006 Postseason · UCLA
42.3
57 primary · 68 efficiency · 6.3 usage
0
100+ receiving yards
0
8+ catch outings
0
2+ TD games
Recruit Profile
Class 2020 · Rating 0.8193
Merrillville · Merrillville, IN
Career Facts
1
Career teams
6
Seasons tracked
342
Career Receiving Yards
Data Context
Coverage spans 6 tracked seasons, 22 games, and base opponent context only. Derived metrics fall back to raw production when share or rating context is missing.