Running back, Presbyterian, 2023–⁠25

Zach Switzer

Number
No. 5
Height
5′11″
Weight
195 lb
Class (2025)
Senior
Hometown
Spring Hill, TN

Zach Switzer played running back at Presbyterian (2023–⁠25).

Career highs

158rushing yards, career highvs. Morehead State, 20252rushing touchdowns, career highfour times; last at Butler, 2025

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2023Presbyterian562234.0028
2024Presbyterian663275.0381
2025Presbyterian1357795.8979
Career2571,3295.21281

Returns

SeasonTeamKRYdsTDPRYdsTD
2023Presbyterian1320–––
2024Presbyterian1643611210
2025Presbyterian163670–––
Career3383511210

Receiving

SeasonTeamRecYdsAvgTDLong
2023Presbyterian12998.3050
2024Presbyterian2125112.0267
2025Presbyterian3131610.2431
Career6466610.4667

Season lines from CollegeFootballData, regular season and bowls. A dash: the source has no number for that season (often an FCS season), and career totals count only the numbers on file.

On the roster

SeasonTeamNo.PosClassHtWt
2023Presbyterian5RBSo.
2024Presbyterian5RBJr.
2025Presbyterian5RBSr.5′11″195

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
2025Presbyterian (FCS)1670.2894th (n=576)0.1047.522%

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 Presbyterian 12 games, 779 rushing yards, 9 TD
DateOpponentResultCarRush ydsRush TDKRYdsPR
Aug 30atMercerW 15–⁠109331111–
Sep 6atFurmanW 39–⁠3816670–––
Sep 13vs.ErskineW 42–⁠1412751353–
Sep 20vs.BLUEFIELDW 76–⁠311532272–
Sep 27vs.Morehead StateW 41–⁠061582119–
Oct 11atButlerW 31–⁠2513752–––
Oct 18vs.StetsonW 42–⁠75190115–
Oct 25atDaytonL 19–⁠3519820249–
Nov 1vs.ValparaisoW 43–⁠149470125–
Nov 8atDavidsonL 13–⁠1414861–––
Nov 15atSt. Thomas (MN)W 23–⁠99210114–
Nov 22vs.MaristW 29–⁠25126304109–
2024 Presbyterian 11 games, 327 rushing yards, 3 TD
DateOpponentResultCarRush ydsRush TDKRYdsPR
Aug 29atMercerL 10–⁠63470123–
Sep 7atErskineW 31–⁠1475002112–
Sep 14vs.Virginia LynchburgW 52–⁠05371––1
Sep 21vs.Gardner-WebbL 21–⁠423100118–
Sep 29vs.DavidsonL 37–⁠4812382258–
Oct 5atSan DiegoL 21–⁠279270114–
Oct 12atMorehead StateL 7–⁠1410390357–
Oct 19vs.DrakeL 16–⁠197870124–
Nov 2vs.DaytonW 28–⁠7–––123–
Nov 16atMaristW 42–⁠235100382–
Nov 23vs.ButlerW 30–⁠274220125–
2023 Presbyterian 11 games, 223 rushing yards
DateOpponentResultCarRush ydsRush TDKRYdsPR
Sep 2atMurray StateL 10–⁠41410–––
Sep 9vs.Virginia LynchburgW 48–⁠179440–––
Sep 16atWoffordW 23–⁠20200–––
Sep 30atButlerL 17–⁠276210–––
Oct 7vs.StetsonL 24–⁠289430–––
Oct 14atDaytonW 20–⁠176310–––
Oct 21vs.MaristL 10–⁠198350–––
Oct 28atDavidsonL 28–⁠45470–––
Nov 4vs.San DiegoL 13–⁠233330–––
Nov 11atDrakeL 14–⁠16490–––
Nov 18vs.Morehead StateW 31–⁠271−10132–

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.