Receiver, VMI, 2012–⁠15

Cody Shirley

Cody Shirley played receiver at VMI (2012–⁠15).

Receiving

SeasonTeamRecYdsAvgTDLong
2015VMI133.003

Rushing

SeasonTeamCarYdsAvgTDLong
2012VMI242.003

Season lines from CollegeFootballData, regular season and bowls.

Per play

SeasonTeamPlaysEPA/playPctileMedianTotalUsage
2015VMI (FCS)1-0.11––-0.1–

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

2015 VMI 1 game, 1 catch, 3 yards
DateOpponentResultRecYdsTDLongRush
Sep 3atBall StateL 36–⁠481303–

No box score in the source for Sep 12 vs. Morehead State; Sep 19 at Richmond; Sep 26 at Furman; Oct 3 vs. Bucknell; Oct 10 vs. Samford; Oct 17 vs. Chattanooga; Oct 24 at Mercer; Oct 31 vs. Wofford; Nov 7 at The Citadel; Nov 21 vs. Western Carolina, so those games are not listed.

2012 VMI 1 game, 4 rushing yards
DateOpponentResultRecYdsTDLongRush
Sep 22atNavyL 3–⁠41––––4

No box score in the source for Sep 1 at Delaware State; Nov 10 vs. The Citadel, so those games are 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.