Navy, 2008–09
Cory Finnerty
- Number
- No. 23
- Height
- 5′10″
- Hometown
- Ventura, CA
Cory Finnerty played at Navy (2008–09).
Rushing
Receiving
Season lines from CollegeFootballData, regular season and bowls. * That team-season’s player lines are missing part of the team’s yards in our source, so these numbers may be short.
On the roster
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.
Game by game
2009 Navy 10 games, 77 rushing yards, 1 TD
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Sep 5 | at Ohio State | L 27–31 | 2 | 2 | 0 | 1 | 5 | 0 |
| Sep 12 | vs. Louisiana Tech | W 32–14 | 3 | 23 | 1 | – | – | – |
| Sep 26 | vs. Western Kentucky | W 38–22 | 1 | 7 | 0 | 1 | 29 | 1 |
| Oct 3 | vs. Air Force | W 16–13 | 2 | 0 | 0 | 1 | 12 | 0 |
| Oct 10 | at Rice | W 63–14 | 1 | −1 | 0 | – | – | – |
| Oct 17 | at SMU | W 38–35 | 1 | −2 | 0 | – | – | – |
| Oct 24 | vs. Wake Forest | W 13–10 | 1 | 9 | 0 | – | – | – |
| Oct 31 | vs. Temple | L 24–27 | 1 | 7 | 0 | 1 | −4 | 0 |
| Nov 28 | at Hawai’i | L 17–24 | – | – | – | 1 | 7 | 0 |
| Dec 31 ✦ | vs. Missouri | W 35–13 | 5 | 32 | 0 | 1 | 8 | 0 |
2008 Navy 7 games, 71 rushing yards, 1 TD
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Aug 30 | vs. Towson | W 41–13 | 2 | 19 | 0 | – | – | – |
| Sep 5 | at Ball State | L 23–35 | – | – | – | 2 | 13 | 0 |
| Sep 27 | atWake Forest | W 24–17 | 1 | −2 | 0 | 1 | 19 | 0 |
| Oct 18 | vs. Pittsburgh | L 21–42 | 1 | 3 | 0 | – | – | – |
| Oct 25 | vs.SMU | W 34–7 | 2 | 16 | 0 | – | – | – |
| Nov 1 | vs.Temple | W 33–27 | 1 | 13 | 0 | 1 | 5 | 0 |
| Nov 15 | vs. Notre Dame | L 21–27 | 1 | 22 | 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.