Usage Score
6.3
Player Dossier
2007-2010Buffalo
Kyle Brey
TE • 6'2" • Granger, IN, USA
Reliable chain-moverPossession profile
Kyle Brey reads as a reliable chain-mover based on recent role and receiving efficiency.
Efficiency
40
Consistency
100
Season Value
41.3
Career Arc
Value trend by season
Best season by value score: 2008 Regular Season · Buffalo
07080910
Snapshot
- Career Teams
- 1
- Seasons Tracked
- 4
- Program Path
- Buffalo
- Peak Game
- Peak game by takeover score: Temple
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.
Kyle Brey, TE. Best season Best season by value score: 2008 Regular Season · Buffalo. Kyle Brey reads as a reliable chain-mover based on recent role and receiving efficiency.
Player insights
Lead takeaway
Best season by value score: 2008 Regular Season
Buffalo paired 31 primary output with 40 efficiency.
Supporting note
2009 Regular Season role shape
target-driven usage with 40 efficiency.
Supporting note
Career value cooled off
2010 Regular Season fell back from the prior stop by season value score.
Supporting note
Peak game by takeover score: Central Michigan
Loss 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.
2009 Regular Season · Buffalo
Games
1
Receiving Yards / G
6
Efficiency
40
Usage
6.3
Consistency
100
Best Game by takeover score
Central Michigan
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
Receiving Yards
Top game by takeover score
Central Michigan
Best efficiency game
40 vs Central Michigan
| Result | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| Sat 10/3 | vs Central Michigan | L 13-20 | — | 1 | 6 | 6 | 6 | 0 | 6 |
Career Arc
Track team changes, role shifts, and season-to-season movement.
- 1
Buffalo
2007-2010
Opening stop
Season Progression
2007200820092010
| Season | Team | Primary | Efficiency | Usage | Delta |
|---|---|---|---|---|---|
| 2007 Regular Season | Buffalo | 6 | 20 | 5.3 | — |
| 2008 Regular Season | Buffalo | 31 | 40 | 10.7 | 25 |
| 2009 Regular Season | Buffalo | 6 | 40 | 6.3 | -25 |
| 2010 Regular Season | Buffalo | 0 | — | — | -6 |
Signature Performances
Top Games
#1 Featured game
Temple
Win with an explosive receiving profile.
21
Primary metric
21 receiving yards with a 46.7 efficiency score.
#2
Central Michigan
6
Primary metric
Loss with an explosive receiving profile.
6 receiving yards with a 40 efficiency score.
#3
Ball State
4
Primary metric
Loss with an explosive receiving profile.
4 receiving yards with a 26.7 efficiency score.
#4
Western Michigan
10
Primary metric
Loss with an explosive receiving profile.
10 receiving yards with a 33.3 efficiency score.
#5
Penn State
2
Primary metric
Loss with an explosive receiving profile.
2 receiving yards with a 13.3 efficiency score.
Top Seasons
#1 Season by value score
2008 Regular Season · Buffalo
31 primary output · 40 efficiency · 10.7 usage
54.8
#2
2009 Regular Season · Buffalo
41.3
6 primary · 40 efficiency · 6.3 usage
#3
2007 Regular Season · Buffalo
29.1
6 primary · 20 efficiency · 5.3 usage
Milestones
0
100+ receiving yards
0
8+ catch outings
0
2+ TD games
Bio, Recruit, and Data Context
Recruit Profile
2★
Class 2006 · Rating 0.7222
Penn · Mishawaka, IN
- Committed To
- Buffalo
- Commit Date
- Jan 1, 2006
Career Facts
1
Career teams
4
Seasons tracked
43
Career Receiving Yards
Data Context
Coverage spans 4 tracked seasons, 5 games, and base opponent context only. Derived metrics fall back to raw production when share or rating context is missing.