Running back, Stony Brook (from Virginia Tech), 2023–⁠26

Jeremiah Coney

Number
No. 4
Height
6′0″
Weight
200 lb
Class (2026)
Senior
Hometown
Richmond, VA

Jeremiah Coney plays running back for Stony Brook, after Virginia Tech (2023–⁠25). Last time out, against UAlbany: 4 carries, 8 yards, 1 TD; 1 catch, 6 yards.

2026 so far

254 rushing yards, 6 TD

Last game: 4 carries, 8 yards, 1 TD; 1 catch, 6 yards vs. UAlbany, L 31–⁠48

Next game: at Bryant, Oct 24

Game by game this season, rushing yards
  1. 13@DSU
  2. 17LIN
  3. 89@BALL
  4. 90URI
  5. 12@FOR
  6. 25@TOW
  7. 8UALB

Filled bars: wins; outlined: losses.

Career highs

96rushing yards, career highat Syracuse, 20243rushing touchdowns, career highvs. Rhode Island, 2026

Rushing

Rushing yards, season by season, with his team’s record

* The season in progress, so far.

SeasonTeamCarYdsAvgTDLong
2023Virginia Tech11302.708
2024Virginia Tech321795.6047
2025Virginia Tech8475.9021
2026Stony Brook642544.0666
Career1155104.4666

Receiving

SeasonTeamRecYdsAvgTDLong
2025Virginia Tech3155.009
2026Stony Brook7436.1017
Career10585.8017

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2023Virginia Tech4RBFr.
2024Virginia Tech4RBSo.
2025Virginia Tech4RBJr.
2026Stony Brook4RBSr.6′0″200

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/playPctileMedianTotalUsageAdj. rush
2023Virginia Tech11-0.13––-1.4––
2024Virginia Tech32-0.06––-1.87%0.01
2025Virginia Tech70.40––2.8––
2026Stony Brook (FCS)750.0640th (n=478)0.104.715%–

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

2026 Stony Brook 7 games, 254 rushing yards, 6 TD
DateOpponentResultCarYdsTDLongRecRec yds
Aug 27atDelaware StateL 34–⁠417130415
Sep 3vs.LindenwoodW 36–⁠3271705222
Sep 12atBall StateL 17–⁠4198926611
Sep 19vs.Rhode IslandW 56–⁠242090313––
Sep 26atFordhamW 31–⁠167120529
Oct 10atTowsonW 31–⁠24102506––
Oct 17vs.UAlbanyL 31–⁠48481416
2025 Virginia Tech 3 games, 47 rushing yards
DateOpponentResultCarYdsTDLongRecRec yds
Aug 31vs.South CarolinaL 11–⁠24416011––
Sep 6vs.VanderbiltL 20–⁠44225021––
Sep 20vs.WoffordW 38–⁠62605315
2024 Virginia Tech 7 games, 179 rushing yards
DateOpponentResultCarYdsTDLongRecRec yds
Sep 14atOld DominionW 37–⁠1751807––
Oct 5atStanfordW 31–⁠72403––
Oct 17vs.Boston CollegeW 42–⁠21221019––
Nov 2atSyracuseL 31–⁠38996047––
Nov 23atDukeL 28–⁠31522011––
Nov 30vs.VirginiaW 37–⁠172808––
Jan 3 ✦vs.MinnesotaL 10–⁠2471005––
2023 Virginia Tech 3 games, 30 rushing yards
DateOpponentResultCarYdsTDLongRecRec yds
Oct 26vs.SyracuseW 38–⁠103204––
Nov 11atBoston CollegeW 48–⁠223705––
Dec 27 ✦vs.TulaneW 41–⁠2052108––

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.