Zach Abey
Photo: Chairman of the Joint Chiefs of Staff, CC BY 2.0, via Wikimedia Commons

Receiver, Navy, 2015–⁠18

Zach Abey

Number
No. 9
Height
6′2″
Weight
212 lb
Class (2018)
Senior
Hometown
Pasadena, MD

Wikipedia readers: about 202 a month over the past year

Zach Abey played receiver at Navy (2015–⁠18).

At a glance

Best season
1,413
Rushing yards, 2017 (Navy, 7–⁠6)
Best game
235 yards
At Florida Atlantic, week 1, 2017: No. 2 rushing game in FBS that week
National rank
No. 8
In FBS in rushing touchdowns, 2017

Career highs

167passing yards, career highat Tulane, 2018235rushing yards, career highat Florida Atlantic, 20175rushing touchdowns, career highvs. Virginia, 2017

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2016Navy703845.5655
2017Navy2931,4134.81975
2018Navy1253062.41415
Career4882,1034.33975

Passing

SeasonTeamCmpAttPctYdsY/ATDInt
2016Navy203557.135210.114
2017Navy317243.180511.277
2018Navy122941.42468.512
Career6313646.31,40310.3913

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2015Navy9WRFr.
2016Navy9WRSo.
2017Navy9WRJr.
2018Navy9WRSr.6′2″212

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
2016Navy1050.218th (n=489)0.5222.536%0.19
2017Navy3250.2916th (n=507)0.5295.741%0.24
2018Navy1570.177th (n=497)0.5326.521%0.23

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

2018 Navy 11 games, 306 rushing yards, 14 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 1atHawai’iL 41–⁠5951747––
Sep 8vs.MemphisW 22–⁠215613––
Sep 15vs.LehighW 51–⁠2151214––
Sep 22atSMUL 30–⁠315613––
Oct 20vs.HoustonL 36–⁠491111––
Oct 27vs.Notre DameL 22–⁠444321––
Nov 3atCincinnatiL 0–⁠42283709––
Nov 10atUCFL 24–⁠352685215––
Nov 17vs.TulsaW 37–⁠2926128215––
Nov 24atTulaneL 28–⁠29141105137
Dec 8vs.ArmyL 10–⁠176004––
2017 Navy 12 games, 805 passing yards, 7 TD; 1,413 rushing yards, 19 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 1atFlorida AtlanticW 42–⁠1932235240––
Sep 9vs.TulaneW 23–⁠2129108054––
Sep 23vs.CincinnatiW 42–⁠3220128253––
Sep 30atTulsaW 31–⁠2136185313––
Oct 7vs.Air ForceW 48–⁠4529214275––
Oct 14atMemphisL 27–⁠3037146328––
Oct 21vs.UCFL 21–⁠3125126114––
Nov 2atTempleL 26–⁠34256001415
Nov 18atNotre DameL 17–⁠242987113––
Nov 24atHoustonL 14–⁠24163308––
Dec 9vs.ArmyL 13–⁠142302––
Dec 28 ✦vs.VirginiaW 49–⁠71388539––
2016 Navy 5 games, 384 rushing yards, 6 TD
DateOpponentResultCarYdsTDLongRecRec yds
Nov 19atEast CarolinaW 66–⁠3151606––
Nov 26atSMUW 75–⁠317111155––
Dec 3vs.TempleL 10–⁠341470147––
Dec 10vs.ArmyL 17–⁠211973241––
Dec 23 ✦vs.Louisiana TechL 45–⁠4825114230––

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.