Quarterback, Richmond, 2022–⁠26

Ashten Snelsire

Number
No. 18
Height
6′3″
Weight
233 lb
Class (2026)
Senior
Hometown
Berlin, MD

Ashten Snelsire plays quarterback for Richmond. Last time out, at Fordham: 24 of 39, 122 yards, 1 INT; 6 carries, −10 yards. Snelsire leads Richmond in passing touchdowns and passing yards this season.

2026 so far

1,365 passing yards, 11 TD

Last game: 24 of 39, 122 yards, 1 INT; 6 carries, −10 yards at Fordham, L 14–⁠20

Next game: vs. Colgate, Oct 24

Game by game this season, passing yards
  1. 199BUCK
  2. 261@HOW
  3. 76@NCSU
  4. 322GTWN
  5. 167FUR
  6. 218@LAF
  7. 122@FOR

Filled bars: wins; outlined: losses.

Career highs

322passing yards, career highvs. Georgetown, 20264touchdown passes, career highat Bucknell, 2025

Team titles: Coastal Athletic Association champions, 2023 and 2024

Passing

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

* The season in progress, so far.

SeasonTeamCmpAttPctYdsY/ATDInt
2023Richmond2728.6131.901
2024Richmond77100.0527.400
2025Richmond5811152.38487.685
2026Richmond14025255.61,3655.4117
Career20737754.92,2786.01913

Rushing

SeasonTeamCarYdsAvgTDLong
2023Richmond471.808
2024Richmond263.0010
2025Richmond531883.5315
2026Richmond30461.5120
Career892472.8420

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2022Richmond18QBRS
2023Richmond18QBFr.
2024Richmond18QBSo.
2025Richmond18QBJr.
2026Richmond18QBSr.6′3″233

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
2023Richmond (FCS)5-0.28––-1.4–
2024Richmond (FCS)41.28––5.1–
2025Richmond (FCS)1650.2243rd (n=314)0.2436.533%
2026Richmond (FCS)2750.0311th (n=273)0.217.157%

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 Richmond 7 games, 1,365 passing yards, 11 TD
DateOpponentResultCmpAttYdsTDIntRush
Aug 29vs.BucknellW 35–⁠141728199304
Sep 5atHowardW 28–⁠21193526130−37
Sep 11atNC StateL 0–⁠738237601–
Sep 19vs.GeorgetownW 24–⁠2129493221011
Sep 26vs.FurmanW 13–⁠91940167139
Oct 3atLafayetteW 40–⁠3124382183269
Oct 10atFordhamL 14–⁠20243912201−10
2025 Richmond 8 games, 848 passing yards, 8 TD
DateOpponentResultCmpAttYdsTDIntRush
Sep 13atNorth CarolinaL 6–⁠4137280133
Sep 20vs.VMIW 38–⁠141122004
Sep 27vs.HowardW 13–⁠12414351131
Oct 4atBucknellL 28–⁠3316273074351
Oct 11atColgateW 24–⁠1913191991020
Nov 8atGeorgetownW 31–⁠24510114206
Nov 15vs.LafayetteL 28–⁠351327990019
Nov 22atWilliam & MaryW 28–⁠2136440024
2024 Richmond 2 games, 52 passing yards
DateOpponentResultCmpAttYdsTDIntRush
Sep 14vs.Charleston SouthernW 38–⁠033290010
Oct 26atBryantW 41–⁠14442300−4
2023 Richmond 2 games, 13 passing yards
DateOpponentResultCmpAttYdsTDIntRush
Sep 23atStony BrookW 20–⁠19137008
Sep 30vs.HamptonL 14–⁠3114601−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.