Receiver, James Madison, 2025–26
Michael Scott
- Number
- No. 17
- Height
- 5′7″
- Weight
- 160 lb
- Class (2026)
- Sophomore
- Hometown
- York, PA
Michael Scott plays receiver for James Madison. Last time out, against Georgia State: 4 catches, 44 yards, 1 TD.
2026 so far
19 catches, 241 yards, 2 TD
Last game: 4 catches, 44 yards, 1 TD vs. Georgia State, W 49–22
Next game: at App State, Oct 22
Filled bars: wins; outlined: losses.
Team titles: Sun Belt champions, 2025
Receiving
* The season in progress, so far.
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2025 | James Madison | 8 | 85 | 10.6 | 1 | 32 |
| 2026 | James Madison | 19 | 241 | 12.7 | 2 | 29 |
| Career | 27 | 326 | 12.1 | 3 | 32 | |
Returns
| Season | Team | KR | Yds | TD | PR | Yds | TD |
|---|---|---|---|---|---|---|---|
| 2025 | James Madison | – | – | – | 2 | 7 | 0 |
| 2026 | James Madison | 12 | 465 | 0 | 11 | 220 | 2 |
| Career | 12 | 465 | 0 | 13 | 227 | 2 | |
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 |
|---|---|---|---|---|---|---|
| 2025 | James Madison | 17 | WR | Fr. | ||
| 2026 | James Madison | 17 | WR | So. | 5′7″ | 160 |
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 |
|---|---|---|---|---|---|---|---|
| 2025 | James Madison | 16 | 0.39 | – | – | 6.3 | – |
| 2026 | James Madison | 33 | 0.50 | 59th (n=829) | 0.43 | 16.4 | 8% |
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
2026 James Madison 7 games, 19 catches, 241 yards, 2 TD
| Date | Opponent | Result | Rec | Rec yds | Rec TD | KR | Yds | PR |
|---|---|---|---|---|---|---|---|---|
| Sep 5 | vs. Liberty | W 20–13 | – | – | – | 1 | 36 | 1 |
| Sep 12 | vs. Wagner | W 87–3 | 3 | 45 | 0 | 2 | 109 | 3 |
| Sep 19 | at San Diego State | W 26–13 | 2 | 22 | 0 | – | – | 3 |
| Sep 26 | at Old Dominion | W 46–20 | 2 | 19 | 1 | 2 | 105 | 1 |
| Oct 3 | vs. Marshall | W 45–17 | 4 | 43 | 0 | 2 | 64 | 3 |
| Oct 10 | at Georgia Southern | W 27–24 | 4 | 68 | 0 | 2 | 31 | – |
| Oct 17 | vs. Georgia State | W 49–22 | 4 | 44 | 1 | 3 | 120 | – |
2025 James Madison 5 games, 8 catches, 85 yards, 1 TD
| Date | Opponent | Result | Rec | Rec yds | Rec TD | KR | Yds | PR |
|---|---|---|---|---|---|---|---|---|
| Aug 30 | vs. Weber State | W 45–10 | 4 | 38 | 0 | – | – | – |
| Sep 5 | at Louisville | L 14–28 | – | – | – | – | – | 1 |
| Nov 15 | vs. App State | W 58–10 | 1 | 5 | 0 | – | – | – |
| Nov 22 | vs. Washington State | W 24–20 | 1 | 5 | 0 | – | – | – |
| Nov 29 | at Coastal Carolina | W 59–10 | 2 | 37 | 1 | – | – | 1 |
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.