Running back, James Madison, 2019–22
Percy Agyei-Obese
- Number
- No. 31
- Height
- 6′0″
- Weight
- 211 lb
- Class (2022)
- Senior
- Hometown
- Frederick, MD
Percy Agyei-Obese played running back at James Madison (2019–22).
Career highs
158rushing yards, career highat Arkansas State, 20222rushing touchdowns, career highthree times; last vs. Georgia State, 2022Team titles: Coastal Athletic Association Football champions, 2019 and 2021
Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2019 | James Madison | 8 | 29 | 3.6 | 0 | 7 |
| 2022 | James Madison | 159 | 908 | 5.7 | 8 | 36 |
| Career | 167 | 937 | 5.6 | 8 | 36 | |
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 | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2019 | James Madison | 31 | RB | Fr. | ||
| 2022 | James Madison | 31 | RB | Sr. | 6′0″ | 211 |
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 | Adj. rush |
|---|---|---|---|---|---|---|---|---|
| 2019 | James Madison (FCS) | 8 | -0.41 | – | – | -3.3 | – | – |
| 2022 | James Madison | 161 | 0.20 | 67th (n=470) | 0.14 | 31.5 | 22% | 0.20 |
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). Adjusted pass and rush: EPA per play adjusted for the defenses faced (CollegeFootballData’s WEPA). From CollegeFootballData, 2013 on.
Game by game
2022 James Madison 10 games, 908 rushing yards, 8 TD
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 3 | vs. | W 44–7 | 15 | 82 | 0 | 12 | – | – |
| Sep 10 | vs. | W 63–7 | 12 | 88 | 2 | 34 | – | – |
| Oct 1 | vs. | W 40–13 | 6 | 26 | 0 | 7 | – | – |
| Oct 8 | at | W 42–20 | 21 | 158 | 2 | 31 | – | – |
| Oct 15 | at | L 38–45 | 18 | 106 | 0 | 23 | 2 | 11 |
| Oct 22 | vs. | L 12–26 | 20 | 96 | 0 | 23 | – | – |
| Nov 5 | at | L 10–34 | 24 | 102 | 1 | 21 | – | – |
| Nov 12 | at | W 37–3 | 16 | 82 | 1 | 21 | – | – |
| Nov 19 | vs. | W 42–40 | 20 | 89 | 2 | 36 | – | – |
| Nov 26 | vs. | W 47–7 | 7 | 79 | 0 | 31 | – | – |
2019 James Madison 1 game, 29 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Aug 31 | at | L 13–20 | 8 | 29 | 0 | 7 | – | – |
No box score in the source for Sep 7 vs. Saint Francis; Sep 14 vs. Morgan State; Sep 21 at Chattanooga; Sep 28 at Elon; Oct 5 at Stony Brook; Oct 12 vs. Villanova; Oct 19 at William & Mary; Oct 26 vs. Towson; Nov 9 vs. New Hampshire; Nov 16 vs. Richmond; Nov 23 at Rhode Island; Dec 7 vs. Monmouth; Dec 14 vs. Northern Iowa; Dec 21 vs. Weber State; Jan 11 at North Dakota 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.
