Receiver, Purdue, 2016–20
Malcolm Dotson
- Number
- No. 83
- Height
- 6′2″
- Weight
- 200 lb
- Class (2020)
- Senior
- Hometown
- Indianapolis, IN
Malcolm Dotson played receiver at Purdue (2016–20).
Defense
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2016 | Purdue | 83 | WR | Yr 1 | ||
| 2017 | Purdue | 83 | WR | Yr 2 | ||
| 2018 | Purdue | 83 | WR | Yr 3 | ||
| 2019 | Purdue | 83 | WR | Yr 4 | ||
| 2020 | Purdue | 83 | WR | Sr. (Yr 5) | 6′2″ | 200 |
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
2019 Purdue 2 games, 2 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Oct 5 | at Penn State | L 7–35 | 1 | 1 | 0 | 0 | 0 |
| Oct 19 | at Iowa | L 20–26 | 1 | 1 | 0 | 0 | 0 |
2018 Purdue 3 games, 3 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 29 | at Nebraska | W 42–28 | 1 | 0 | 0 | 0 | 0 |
| Oct 20 | vs. Ohio State | W 49–20 | 1 | 1 | 0 | 0 | 0 |
| Nov 17 | vs. Wisconsin | L 44–47 | 1 | 1 | 0 | 0 | 0 |
2016 Purdue 7 games, 7 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 3 | vs. Eastern Kentucky | W 45–24 | 1 | 1 | 0 | 0 | 0 |
| Oct 1 | at Maryland | L 7–50 | 1 | 1 | 0 | 0 | 0 |
| Oct 22 | atNebraska | L 14–27 | 1 | 1 | 0 | 0 | 0 |
| Oct 29 | vs.Penn State | L 24–62 | 1 | 1 | 0 | 0 | 0 |
| Nov 12 | vs. Northwestern | L 17–45 | 1 | 1 | 0 | 0 | 0 |
| Nov 19 | vs.Wisconsin | L 20–49 | 1 | 0 | 0 | 0 | 0 |
| Nov 26 | at Indiana | L 24–26 | 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.