Running back, South Dakota, 2015–17
Michael Fredrick
- Number
- No. 14
- Height
- 5′11″
- Weight
- 175 lb
- Hometown
- Ewa Beach, HI
Michael Fredrick played running back at South Dakota (2015–17).
Career highs
81rushing yards, career highat Bowling Green, 2017Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2015 | South Dakota | 8 | 19 | 2.4 | 0 | 6 |
| 2016 | South Dakota | 2 | 4 | 2.0 | 0 | 4 |
| 2017 | South Dakota | 16 | 81 | 5.1 | 1 | 17 |
| Career | 26 | 104 | 4.0 | 1 | 17 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Ht | Wt |
|---|---|---|---|---|---|
| 2015 | South Dakota | 14 | RB | ||
| 2016 | South Dakota | 14 | RB | ||
| 2017 | South Dakota | 14 | RB | 5′11″ | 175 |
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.
Per play
| Season | Team | Plays | EPA/play | Pctile | Median | Total | Usage |
|---|---|---|---|---|---|---|---|
| 2016 | South Dakota (FCS) | 2 | -0.06 | – | – | -0.1 | – |
| 2017 | South Dakota (FCS) | 19 | 0.21 | – | – | 4.1 | – |
Expected points added: how much the player’s plays moved the team’s expected score, per play and in total. Plays: total EPA divided by EPA per play, the plays the source credits to him (for a receiver roughly his catches and runs, not every target; for a passer, not every attempt), so it can differ from attempts plus carries. Percentile: against the position’s regulars that season across all divisions on file (quarterbacks with 150+ plays, backs 60+, receivers and tight ends 30+), with how many there were (n) and their median; a dash means too few plays to rank. A season in progress uses the full-season bar scaled by games played, never below 75 plays for quarterbacks, 30 for backs and 20 for receivers. The cohort grows or shrinks with the source’s coverage each season (2025 lists far more players), so compare percentiles rather than raw EPA across years. FCS seasons are marked. Usage: the share of the team’s plays the player was part of (shown from 20 plays). From CollegeFootballData, 2013 on.
Game by game
2017 South Dakota 1 game, 81 rushing yards, 1 TD
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 9 | at Bowling Green | W 35–27 | 16 | 81 | 1 | 17 | 3 | 25 |
No box score in the source for Sep 2 at Drake; Sep 16 vs. North Dakota; Sep 30 at Western Illinois; Oct 7 vs. Youngstown State; Oct 14 vs. Indiana State; Oct 21 at Illinois State; Oct 28 vs. Southern Illinois; Nov 4 at Northern Iowa; Nov 11 at North Dakota State; Nov 18 vs. South Dakota State; Nov 25 at Nicholls; Dec 2 at Sam Houston, so those games are not listed.
2016 South Dakota 1 game, 4 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 1 | at New Mexico | L 21–48 | 2 | 4 | 0 | 4 | – | – |
No box score in the source for Sep 10 vs. Weber State; Sep 17 at North Dakota; Oct 1 at Youngstown State; Oct 8 vs. Northern Iowa; Oct 15 at Indiana State; Oct 22 vs. Illinois State; Oct 29 vs. Western Illinois; Nov 5 at Southern Illinois; Nov 12 at South Dakota State; Nov 19 vs. North Dakota State, so those games are not listed.
2015 South Dakota 1 game, 19 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 5 | at Kansas State | L 0–34 | 8 | 19 | 0 | 6 | – | – |
No box score in the source for Sep 13 at UC Davis; Sep 19 vs. Drake; Oct 3 vs. Youngstown State; Oct 10 at Western Illinois; Oct 17 at North Dakota State; Oct 24 vs. Missouri State; Oct 31 at Northern Iowa; Nov 7 vs. Southern Illinois; Nov 14 vs. South Dakota State; Nov 21 at Illinois 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.