Running back, Furman, 2022–⁠26

Ben Croasdale

Number
No. 25
Height
5′11″
Weight
202 lb
Class (2026)
Senior
Hometown
Dallas, TX

Ben Croasdale plays running back for Furman. Last time out, at Tennessee Tech: 15 carries, 33 yards; 3 catches, 36 yards. Croasdale leads Furman in rushing touchdowns and rushing yards this season.

2026 so far

305 rushing yards, 3 TD

Last game: 15 carries, 33 yards; 3 catches, 36 yards at Tennessee Tech, L 15–⁠20

Next game: vs. Samford, Oct 24

Game by game this season, rushing yards
  1. 67ANSC
  2. 7@TENN
  3. 74@MER
  4. 24SCST
  5. 7@RICH
  6. 93WOF
  7. 33@TNTC

Filled bars: wins; outlined: losses.

Career highs

93rushing yards, career highvs. Wofford, 20262rushing touchdowns, career highvs. Anderson (SC), 20267catches, career highvs. Wofford, 2026

Team titles: Southern champions, 2023

Rushing

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

* The season in progress, so far.

SeasonTeamCarYdsAvgTDLong
2023Furman3237.7019
2024Furman7263.7011
2025Furman613135.1250
2026Furman663054.6347
Career1376674.9550

Receiving

SeasonTeamRecYdsAvgTDLong
2025Furman7598.4020
2026Furman131118.5017
Career201708.5020

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2022Furman25RBRS
2023Furman25RBFr.
2024Furman25RBSo.
2025Furman25RBJr.
2026Furman25RBSr.5′11″202

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
2023Furman (FCS)3-0.06––-0.2–
2024Furman (FCS)6-0.00––0.0–
2025Furman (FCS)70-0.079th (n=576)0.10-5.016%
2026Furman (FCS)810.1459th (n=478)0.1011.617%

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 Furman 7 games, 305 rushing yards, 3 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Aug 27vs.Anderson (SC)W 20–⁠311672140
Sep 5atTennesseeL 9–⁠56270–––
Sep 12atMercerW 20–⁠136741–––
Sep 19vs.South Carolina StateL 17–⁠2082401100
Sep 26atRichmondL 9–⁠133701130
Oct 3vs.WoffordL 25–⁠32219307480
Oct 10atTennessee TechL 15–⁠20153303360
2025 Furman 7 games, 313 rushing yards, 2 TD
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Oct 11atWestern CarolinaL 7–⁠526720–––
Oct 18atWoffordL 13–⁠31230–––
Oct 25vs.The CitadelW 24–⁠1418840–––
Nov 1vs.MercerL 28–⁠523302270
Nov 8atChattanoogaL 28–⁠45104312160
Nov 15vs.VMIW 32–⁠1414701150
Nov 22atClemsonL 10–⁠4583802110
2024 Furman 2 games, 26 rushing yards
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Aug 31atOle MissL 0–⁠764180–––
Sep 14vs.StetsonW 48–⁠7380–––

No box score in the source for Sep 28 vs. Samford, so that game is not listed.

2023 Furman 1 game, 23 rushing yards
DateOpponentResultCarRush ydsRush TDRecRec ydsRec TD
Sep 23vs.MercerW 38–⁠143230–––

No box score in the source for Dec 9 at Montana, 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.