Receiver, Savannah State, 2017–18
Jamichael Baldwin
- Number
- No. 86
- Height
- 5′9″
- Weight
- 165 lb
- Hometown
- Lubbock, TX
Jamichael Baldwin played receiver at Savannah State (2017–18).
Returns
| Season | Team | KR | Yds | TD | PR | Yds | TD |
|---|---|---|---|---|---|---|---|
| 2017 | Savannah State | 2 | 32 | 0 | 1 | 6 | 0 |
| 2018 | Savannah State | 6 | 121 | 0 | – | – | – |
| Career | 8 | 153 | 0 | 1 | 6 | 0 | |
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 | Ht | Wt |
|---|---|---|---|---|---|
| 2017 | Savannah State | 86 | WR | ||
| 2018 | Savannah State | 86 | WR | 5′9″ | 165 |
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 Savannah State 2 games, 6 returns, 121 yards
No box score in the source for Sep 22 at Florida A&M; Sep 29 vs. Bethune-Cookman; Oct 6 vs. Charleston Southern; Oct 13 vs. Morgan State; Oct 27 vs. Norfolk State; Nov 3 at Delaware State; Nov 10 vs. North Carolina A&T; Nov 17 at South Carolina State, so those games are not listed.
2017 Savannah State 1 game, 1 catch, 8 yards
| Date | Opponent | Result | KR | Yds | PR | Yds | TD |
|---|---|---|---|---|---|---|---|
| Sep 9 | at App State | L 7–54 | 2 | 32 | 1 | 6 | 0 |
No box score in the source for Sep 16 at Montana; Sep 23 vs. Florida A&M; Sep 30 at Bethune-Cookman; Oct 7 vs. Hampton; Oct 14 at Morgan State; Oct 21 at Charleston Southern; Oct 28 at Norfolk State; Nov 4 vs. Delaware State; Nov 11 at North Carolina A&T; Nov 18 vs. South Carolina State, so those games are 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.