Receiver, Tennessee Tech, 2025–26
Maury Sullivan
- Number
- No. 2
- Height
- 6′1″
- Weight
- 211 lb
- Class (2026)
- Senior
- Hometown
- St. Louis, MO
Maury Sullivan plays receiver for Tennessee Tech. Last time out, against Eastern Kentucky: 2 catches, 27 yards.
2026 so far
20 catches, 217 yards, 2 TD
Last game: 2 catches, 27 yards vs. Eastern Kentucky, W 49–20
Next game: at The Citadel, Oct 24
Filled bars: wins; outlined: losses.
Career highs
7catches, career highvs. Davidson, 202587receiving yards, career highvs. Gardner-Webb, 2025Team titles: Big South–OVC Football Association champions, 2025
Receiving
* The season in progress, so far.
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2025 | Tennessee Tech | 49 | 596 | 12.2 | 4 | 48 |
| 2026 | Tennessee Tech | 20 | 217 | 10.8 | 2 | 23 |
| Career | 69 | 813 | 11.8 | 6 | 48 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2025 | Tennessee Tech | 2 | WR | Jr. | ||
| 2026 | Tennessee Tech | 2 | WR | Sr. | 6′1″ | 211 |
As each season’s roster listed the player (CollegeFootballData). Classes before the latest listing are counted back from it; “Yr 1” is the year on file where that count can’t place a season he played (a redshirt, transfer or 2020 year); height and weight as last listed.
Per play
| Season | Team | Plays | EPA/play | Pctile | Median | Total | Usage |
|---|---|---|---|---|---|---|---|
| 2025 | Tennessee Tech (FCS) | 72 | 0.41 | 43rd (n=1040) | 0.46 | 29.6 | 9% |
| 2026 | Tennessee Tech (FCS) | 33 | 0.09 | 10th (n=829) | 0.43 | 2.8 | 7% |
Expected points added: how much the player’s plays moved the team’s expected score, per play and in total. Plays: total EPA divided by EPA per play, the plays the source credits to him (for a receiver roughly his catches and runs, not every target; for a passer, not every attempt), so it can differ from attempts plus carries. Percentile: against the position’s regulars that season across all divisions on file (quarterbacks with 150+ plays, backs 60+, receivers and tight ends 30+), with how many there were (n) and their median; a dash means too few plays to rank. A season in progress uses the full-season bar scaled by games played, never below 75 plays for quarterbacks, 30 for backs and 20 for receivers. The cohort grows or shrinks with the source’s coverage each season (2025 lists far more players), so compare percentiles rather than raw EPA across years. FCS seasons are marked. Usage: the share of the team’s plays the player was part of (shown from 20 plays). From CollegeFootballData, 2013 on.
Game by game
2026 Tennessee Tech 6 games, 20 catches, 217 yards, 2 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Aug 29 | vs. Monmouth | W 38–14 | 3 | 44 | 1 | 23 |
| Sep 5 | at Chattanooga | W 24–9 | 5 | 68 | 1 | 22 |
| Sep 26 | at Wofford | W 42–38 | 4 | 28 | 0 | 9 |
| Oct 3 | at Western Carolina | L 20–44 | 2 | 29 | 0 | 17 |
| Oct 10 | vs. Furman | W 20–15 | 4 | 21 | 0 | 12 |
| Oct 17 | vs. Eastern Kentucky | W 49–20 | 2 | 27 | 0 | 21 |
2025 Tennessee Tech 12 games, 49 catches, 596 yards, 4 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Aug 30 | vs.Cumberland (TN) | W 65–0 | 3 | 32 | 0 | 12 |
| Sep 6 | vs.Chattanooga | W 45–17 | 4 | 52 | 1 | 18 |
| Sep 13 | vs. Davidson | W 72–14 | 7 | 78 | 0 | 14 |
| Oct 4 | vs. Western Illinois | W 66–20 | 5 | 72 | 0 | 29 |
| Oct 11 | at Charleston Southern | W 27–13 | 3 | 32 | 1 | 22 |
| Oct 18 | at Lindenwood | W 52–28 | 4 | 31 | 1 | 11 |
| Oct 25 | vs. Southeast Missouri State | W 42–23 | 2 | 24 | 0 | 13 |
| Nov 1 | vs. Gardner-Webb | W 27–21 | 4 | 87 | 0 | 29 |
| Nov 8 | at Eastern Illinois | W 21–9 | 3 | 64 | 1 | 48 |
| Nov 15 | at Kentucky | L 10–42 | 6 | 63 | 0 | 29 |
| Nov 22 | vs. UT Martin | W 20–17 | 3 | 32 | 0 | 12 |
| Nov 29 | vs. North Dakota | L 6–31 | 5 | 29 | 0 | 10 |
Box scores from CollegeFootballData, 2004 on. ✦ postseason; ★ a career high on file.
Is this you, or do you know of something wrong or missing here? Suggest a correction. We check each one against a source before changing the page.