Receiver, Delaware State (from Louisville), 2024–26
Shaun Boykins
- Number
- No. 9
- Height
- 6′1″
- Weight
- 215 lb
- Class (2026)
- Junior
- Hometown
- Radcliff, KY
Shaun Boykins plays receiver for Delaware State, after Louisville (2024–25).
2026 so far
3 catches, 28 yards
Last game: at UAlbany, L 3–28
Next game: vs. North Carolina Central, Oct 23
Filled bars: wins; outlined: losses.
Career highs
101rushing yards, career highvs. Kentucky, 20252rushing touchdowns, career highvs. Bowie State, 2026Rushing
* The season in progress, so far.
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2025 | Louisville | 37 | 190 | 5.1 | 1 | 26 |
| 2026 | Delaware State | 19 | 92 | 4.8 | 2 | 19 |
| Career | 56 | 282 | 5.0 | 3 | 26 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2024 | Louisville | 9 | WR | Fr. | ||
| 2025 | Louisville | 9 | WR | So. | ||
| 2026 | Delaware State | 9 | WR | Jr. | 6′1″ | 215 |
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 |
|---|---|---|---|---|---|---|---|
| 2026 | Delaware State (FCS) | 23 | 0.08 | 9th (n=829) | 0.43 | 1.9 | 9% |
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.
Rushing detail
| Season | Team | Success | Line yards | Second level | Open field | Stuffed |
|---|---|---|---|---|---|---|
| 2025 | Louisville | 57% | 3.20 | 1.90 | 0.90 | 29% |
Where his yards came from, per carry: line yards are the ones credited to the blockers (the first few, and losses), second level the yards 5 to 10 past the line, open field those beyond 10. Success: carries that kept the offense on schedule. Stuffed: carries stopped at or behind the line. From CollegeFootballData, FBS games, 2025 on.
Game by game
2026 Delaware State 4 games, 3 catches, 28 yards
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 12 | vs.Bowie State | W 21–6 | 10 | 87 | 2 | 19 | 2 | 13 |
| Sep 19 | at South Florida | L 17–59 | 4 | −1 | 0 | 6 | 1 | 15 |
| Sep 26 | vs. Towson | W 33–28 | 3 | −1 | 0 | 0 | – | – |
| Oct 3 | at UAlbany | L 3–28 | 2 | 7 | 0 | 7 | – | – |
No box score in the source for Oct 10 vs. Franklin Pierce, so that game is not listed.
2025 Louisville 4 games, 190 rushing yards, 1 TD
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Aug 30 | vs. Eastern Kentucky | W 51–17 | 5 | 40 | 0 | 16 | 1 | 5 |
| Sep 20 | vs. Bowling Green | W 40–17 | 2 | −3 | 0 | 0 | – | – |
| Nov 22 | at SMU | L 6–38 | 8 | 52 | 0 | 26 | – | – |
| Nov 29 | vs. Kentucky | W 41–0 | 22 | 101 | 1 | 12 | – | – |
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.