Defensive back, Boston College, 2025–26
Ashton Cunningham
- Number
- No. 14
- Height
- 5′9″
- Weight
- 170 lb
- Class (2026)
- Sophomore
- Hometown
- Tulsa, OK
Ashton Cunningham plays defensive back for Boston College. Last time out, at SMU: 3 tackles.
2026 so far
7 tackles
Last game: 3 tackles at SMU, L 16–25
Next game: at Georgia Tech, Oct 24
Filled bars: wins; outlined: losses.
Defense
* The season in progress, so far.
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2025 | Boston College | 13 | 9 | 0 | 0 | 3 | 0 |
| 2026 | Boston College | 7 | 6 | 0 | 0 | 1 | 0 |
| Career | 20 | 15 | 0 | 0 | 4 | 0 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2025 | Boston College | 14 | DB | Fr. | ||
| 2026 | Boston College | 14 | DB | So. | 5′9″ | 170 |
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 Boston College 4 games, 7 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 11 | vs. Rutgers | W 28–21 | 1 | 1 | 0 | 0 | 0 |
| Sep 19 | vs. Maine | W 22–16 | 1 | 1 | 0 | 0 | 0 |
| Sep 26 | vs. Virginia Tech | L 14–21 | 2 | 1 | 0 | 0 | 1 |
| Oct 3 | at SMU | L 16–25 | 3 | 3 | 0 | 0 | 0 |
2025 Boston College 5 games, 13 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 13 | at Stanford | L 20–30 | 1 | 1 | 0 | 0 | 0 |
| Sep 27 | vs. California | L 24–28 | 5 | 3 | 0 | 0 | 1 |
| Oct 4 | at Pittsburgh | L 7–48 | 4 | 3 | 0 | 0 | 2 |
| Oct 11 | vs. Clemson | L 10–41 | 2 | 1 | 0 | 0 | 0 |
| Nov 29 | at Syracuse | W 34–12 | 1 | 1 | 0 | 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.