Quarterback, South Carolina State (from East Carolina, Incarnate Word), 2020–⁠25

Ryan Stubblefield

Number
No. 2
Height
6′0″
Weight
205 lb
Class (2025)
Senior
Hometown
Richmond, TX

Ryan Stubblefield played quarterback at East Carolina (2020–⁠22), Incarnate Word (2023) and South Carolina State (2024–⁠25).

Career highs

286passing yards, career highvs. Bethune-Cookman, 202580rushing yards, career highat Charleston Southern, 20252rushing touchdowns, career highthree times; last at Charleston Southern, 2025

Team titles: MEAC champions, 2024 and 2025

Passing

Passing yards, season by season, with his team’s record
SeasonTeamCmpAttPctYdsY/ATDInt
2023Incarnate Word111861.1894.900
2024*South Carolina State334671.746510.152
2025South Carolina State9917556.61,2907.474
Career14323959.81,8447.7126

Rushing

SeasonTeamCarYdsAvgTDLong
2023Incarnate Word3−4−1.300
2024*South Carolina State24301.3336
2025South Carolina State581592.7624
Career851852.2936

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

SeasonTeamNo.PosClassHtWt
2020East Carolina2QB
2021East Carolina2QBRS
2022East Carolina2QBFr.
2023Incarnate Word2QBSo.
2024South Carolina State2QBJr.
2025South Carolina State2QBSr.6′0″205

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

SeasonTeamPlaysEPA/playPctileMedianTotalUsage
2023Incarnate Word (FCS)20-0.40––-8.015%
2024South Carolina State (FCS)450.43––19.514%
2025South Carolina State (FCS)2300.2346th (n=314)0.2453.435%

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

2025 South Carolina State 10 games, 1,290 passing yards, 7 TD
DateOpponentResultCmpAttYdsTDIntRush
Aug 30vs.WoffordW 16–⁠1510171241016
Sep 6atSouth CarolinaL 10–⁠3881490107
Sep 13vs.Bethune-CookmanW 55–⁠4121352861031
Sep 20atSouth FloridaL 14–⁠63714840118
Sep 27atCharleston SouthernL 24–⁠3118241940080
Oct 4vs.Savannah StateW 49–⁠6143020620−8
Oct 11atNorth Carolina A&TW 22–⁠165106401−1
Nov 8vs.HowardW 42–⁠1212801–
Nov 22atDelaware StateW 28–⁠17–––––5
Dec 13 ✦vs.Prairie View A&MW 40–⁠3815292342111
2024 South Carolina State 6 games, 465 passing yards, 5 TD
DateOpponentResultCmpAttYdsTDIntRush
Sep 14atGeorgia SouthernL 14–⁠4201000–
Oct 26vs.Delaware StateW 69–⁠35558710–
Nov 9atHowardW 38–⁠14111600–
Nov 16atMorgan StateW 54–⁠771185200
Nov 23vs.Norfolk StateW 53–⁠2118252642141
Dec 14 ✦vs.Jackson StateL 7–⁠28231301−11

No box score in the source for Oct 19 vs. Fort Valley State, so that game is not listed.

2023 Incarnate Word 2 games, 89 passing yards
DateOpponentResultCmpAttYdsTDIntRush
Sep 23vs.North AmericanW 63–⁠3343700–
Oct 21atMcNeeseW 35–⁠248145200−4

No box score in the source for Nov 11 vs. Northwestern State, so that game is 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.