Kicker, Army, 2019–23
Cole Talley
- Number
- No. 94
- Height
- 6′0″
- Weight
- 205 lb
- Class (2023)
- Senior
- Hometown
- Rockwall, TX
Cole Talley played kicker at Army (2019–23).
Kicking
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2019 | Army | 94 | PK | Yr 1 | ||
| 2020 | Army | 94 | PK | Yr 2 | ||
| 2021 | Army | 94 | PK | Yr 3 | ||
| 2022 | Army | 94 | PK | Yr 4 | ||
| 2023 | Army | 94 | PK | Sr. (Yr 5) | 6′0″ | 205 |
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
| Season | Team | Plays | EPA/play | Pctile | Median | Total | Usage | PAAR |
|---|---|---|---|---|---|---|---|---|
| 2019 | Army | – | – | – | – | – | – | -3.1 (3 att.) |
| 2021 | Army | – | – | – | – | – | – | 2.3 (11 att.) |
| 2023 | Army | – | – | – | – | – | – | -0.7 (1 att.) |
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). PAAR: points a kicker added above a replacement-level kicker, with his field-goal attempts. From CollegeFootballData, 2013 on.
Game by game
2023 Army 3 games, 0 of 1 field goal
| Date | Opponent | Result | FGM | FGA | Long | XP | Pts |
|---|---|---|---|---|---|---|---|
| Sep 9 | vs. Delaware State | W 57–0 | 0 | 1 | 0 | 0 | 0 |
| Sep 23 | at Syracuse | L 16–29 | 0 | 0 | 0 | 1 | 1 |
| Oct 7 | vs. Boston College | L 24–27 | 0 | 0 | 0 | 3 | 3 |
2021 Army 13 games, 8 of 11 field goals
| Date | Opponent | Result | FGM | FGA | Long | XP | Pts |
|---|---|---|---|---|---|---|---|
| Sep 4 | at Georgia State | W 43–10 | 1 | 1 | 22 | 4 | 7 |
| Sep 11 | vs. Western Kentucky | W 38–35 | 1 | 1 | 31 | 5 | 8 |
| Sep 18 | vs. UConn | W 52–21 | 0 | 0 | 0 | 4 | 4 |
| Sep 25 | vs. Miami (OH) | W 23–10 | 1 | 1 | 21 | 2 | 5 |
| Oct 2 | at Ball State | L 16–28 | 0 | 0 | 0 | 2 | 2 |
| Oct 16 | at Wisconsin | L 14–20 | 0 | 1 | 0 | 2 | 2 |
| Oct 23 | vs. Wake Forest | L 56–70 | 0 | 0 | 0 | 8 | 8 |
| Nov 6 | vs. Air Force | W 21–14 | 0 | 1 | 0 | 3 | 3 |
| Nov 13 | vs. Bucknell | W 63–10 | 0 | 0 | 0 | 4 | 4 |
| Nov 20 | vs. Massachusetts | W 33–17 | 1 | 1 | 33 | 2 | 5 |
| Nov 27 | at Liberty | W 31–16 | 1 | 1 | 26 | 4 | 7 |
| Dec 11 | vs. Navy | L 13–17 | 2 | 2 | 32 | 1 | 7 |
| Dec 22 ✦ | vs. Missouri | W 24–22 | 1 | 2 | 41 | 3 | 6 |
2019 Army 7 games, 1 of 3 field goals
| Date | Opponent | Result | FGM | FGA | Long | XP | Pts |
|---|---|---|---|---|---|---|---|
| Aug 30 | vs. Rice | W 14–7 | 0 | 0 | 0 | 2 | 2 |
| Sep 7 | at Michigan | L 21–24 | 0 | 1 | 0 | 3 | 3 |
| Oct 19 | atGeorgia State | L 21–28 | 0 | 0 | 0 | 3 | 3 |
| Oct 26 | vs. San José State | L 29–34 | 1 | 1 | 41 | 2 | 5 |
| Nov 2 | atAir Force | L 13–17 | 0 | 0 | 0 | 1 | 1 |
| Nov 9 | vs.Massachusetts | W 63–7 | 0 | 0 | 0 | 7 | 7 |
| Nov 16 | vs. VMI | W 47–6 | 0 | 1 | 0 | 1 | 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.