Receiver, Miami (OH), 2006–08
Donovan Potter
- Number
- No. 86
- Height
- 6′2″
- Weight
- 197 lb
- Hometown
- Trotwood, OH
Donovan Potter played receiver at Miami (OH) (2006–08).
Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2007* | Miami (OH) | 9 | 74 | 8.2 | 0 | 14 |
| 2008* | Miami (OH) | 9 | 61 | 6.8 | 0 | 13 |
| On file (2007–08) | 18 | 135 | 7.5 | 0 | 14 | |
Season lines from CollegeFootballData, regular season and bowls. * That team-season’s player lines are missing part of the team’s yards in our source, so these numbers may be short.
On the roster
| Season | Team | No. | Pos | Ht | Wt |
|---|---|---|---|---|---|
| 2007 | Miami (OH) | 86 | WR | ||
| 2008 | Miami (OH) | 86 | WR | 6′2″ | 197 |
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
2008 Miami (OH) 7 games, 9 catches, 61 yards
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 6 | at Michigan | L 6–16 | 1 | 6 | 0 | 6 |
| Oct 11 | at Northern Illinois | L 13–17 | 1 | 10 | 0 | 10 |
| Oct 25 | vs. Kent State | L 21–54 | 1 | 13 | 0 | 13 |
| Nov 4 | at Buffalo | L 17–37 | 2 | 14 | 0 | 7 |
| Nov 11 | vs. Ball State | L 16–31 | 2 | 5 | 0 | 3 |
| Nov 21 | at Toledo | L 14–42 | 1 | 1 | 0 | 1 |
| Nov 28 | vs. Ohio | L 26–41 | 1 | 12 | 0 | 12 |
2007 Miami (OH) 4 games, 9 catches, 74 yards
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 8 | at Minnesota | L 35–41 | 1 | 14 | 0 | 14 |
| Sep 15 | vs. Cincinnati | L 10–47 | 3 | 26 | 0 | 12 |
| Nov 24 | atOhio | L 29–38 | 1 | 9 | 0 | 9 |
| Dec 1 | vs. Central Michigan | L 10–35 | 4 | 25 | 0 | 10 |
No box score in the source for Oct 20 at Temple, so that game is not listed.
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.