Defensive line, William & Mary, 2025–26
Brady Echols
- Number
- No. 96
- Height
- 6′2″
- Weight
- 305 lb
- Class (2026)
- Sophomore
- Hometown
- Springfield, VA
Brady Echols plays defensive line for William & Mary. Last time out, at North Carolina Central: 2 tackles.
2026 so far
16 tackles
Last game: 2 tackles at North Carolina Central, W 17–14
Next game: vs. Georgetown, Oct 24
Filled bars: wins; outlined: losses.
Defense
* The season in progress, so far.
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2025 | William & Mary | 3 | 2 | 0.5 | 0 | 0 | 0 |
| 2026 | William & Mary | 16 | 4 | 0 | 0 | 0 | 1 |
| Career | 19 | 6 | 0.5 | 0 | 0 | 1 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2025 | William & Mary | 96 | DL | Fr. | ||
| 2026 | William & Mary | 96 | DL | So. | 6′2″ | 305 |
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.
Game by game
2026 William & Mary 7 games, 16 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Aug 28 | at Villanova | W 35–32 | 2 | 1 | 0 | 0 | 0 |
| Sep 5 | vs. Delaware State | W 22–15 | 3 | 0 | 0 | 0 | 0 |
| Sep 12 | at Lehigh | L 20–44 | 1 | 1 | 0 | 0 | 0 |
| Sep 19 | vs. Fordham | L 27–52 | 2 | 0 | 0 | 0 | 0 |
| Sep 26 | at Duke | L 7–62 | 1 | 0 | 0 | 0 | 0 |
| Oct 3 | vs. Holy Cross | L 14–41 | 5 | 1 | 0 | 0 | 0 |
| Oct 10 | at North Carolina Central | W 17–14 | 2 | 1 | 0 | 0 | 0 |
2025 William & Mary 1 game, 3 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 13 | at Virginia | L 16–55 | 3 | 2 | 0.5 | 0 | 0 |
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.