Cornerback, Purdue, 2015–18
Antonio Blackmon
- Number
- No. 14
- Height
- 6′0″
- Weight
- 195 lb
- Class (2018)
- Senior
- Hometown
- Fort Wayne, IN
Antonio Blackmon played cornerback at Purdue (2015–18).
Career highs
9tackles, career hightwice; last at Michigan State, 2018Defense
Season lines from CollegeFootballData, regular season and bowls. A dash: the source has no number for that season (often an FCS season), and career totals count only the numbers on file.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2015 | Purdue | 14 | CB | Fr. | ||
| 2016 | Purdue | 14 | CB | So. | ||
| 2017 | Purdue | 14 | CB | Jr. | ||
| 2018 | Purdue | 14 | CB | Sr. | 6′0″ | 195 |
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
2018 Purdue 12 games, 60 tackles, 2 INT
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | Int | PD |
|---|---|---|---|---|---|---|---|---|
| Aug 30 | vs. Northwestern | L 27–31 | 5 | 3 | 0 | 0 | 0 | 1 |
| Sep 8 | vs. Eastern Michigan | L 19–20 | 6 | 6 | 1 | 0 | 0 | 0 |
| Sep 15 | vs. Missouri | L 37–40 | 8 | 8 | 0 | 0 | 0 | 1 |
| Sep 22 | vs. Boston College | W 30–13 | 3 | 3 | 0 | 0 | 1 | 0 |
| Sep 29 | at Nebraska | W 42–28 | 9 | 5 | 0 | 0 | 0 | 0 |
| Oct 13 | at Illinois | W 46–7 | 2 | 2 | 0 | 0 | 0 | 1 |
| Oct 20 | vs. Ohio State | W 49–20 | 8 | 6 | 0.5 | 0 | 0 | 2 |
| Oct 27 | at Michigan State | L 13–23 | 9 | 7 | 0 | 0 | 0 | 1 |
| Nov 3 | vs. Iowa | W 38–36 | 1 | 1 | 0 | 0 | 0 | 1 |
| Nov 10 | at Minnesota | L 10–41 | – | – | – | – | 1 | – |
| Nov 17 | vs. Wisconsin | L 44–47 | 5 | 5 | 0 | 0 | 0 | 0 |
| Nov 24 | at Indiana | W 28–21 | 4 | 4 | 0 | 0 | 0 | 0 |
2017 Purdue 6 games, 11 tackles
2016 Purdue 6 games, 9 tackles, 1 INT
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.