Kicker, Colorado State (from Utah), 2020–⁠24

Jordan Noyes

Number
No. 23
Height
5′11″
Weight
195 lb
Class (2024)
Senior
Hometown
Kent, England

Jordan Noyes played kicker at Utah (2020–⁠22) and Colorado State (2023–⁠24).

Career highs

3field goals, career highthree times; last at Nevada, 2024

Team titles: Pac-12 champions, 2021 and 2022

Kicking

Field goals made, season by season, with his team’s record
SeasonTeamFGMFGAPctLongXPPts
2021Utah2450.0332127
2022Utah6875.0433452
2023Colorado State151978.9552974
2024Colorado State141973.7603375
Career375074.060117228

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2020Utah23PKYr 1
2021Utah23PKYr 2
2022Utah23PKYr 3
2023Colorado State23PKYr 4
2024Colorado State23PKSr. (Yr 5)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/playPctileMedianTotalUsagePAAR
2021Utah––––––-2.1 (4 att.)
2022Utah––––––-2.1 (7 att.)
2023Colorado State––––––7.0 (18 att.)
2024Colorado State––––––2.9 (19 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

2024 Colorado State 12 games, 14 of 19 field goals
DateOpponentResultFGMFGALongXPPts
Sep 7vs.Northern ColoradoW 38–⁠17112058
Sep 14vs.ColoradoL 9–⁠28122503
Sep 21vs.UTEPW 27–⁠17223939
Oct 5atOregon StateL 31–⁠39112525
Oct 12vs.San José StateW 31–⁠24115847
Oct 19atAir ForceW 21–⁠1300033
Oct 26vs.New MexicoW 17–⁠6124725
Nov 2atNevadaW 38–⁠213360312
Nov 15vs.WyomingW 24–⁠10132236
Nov 23atFresno StateL 22–⁠2800022
Nov 29vs.Utah StateW 42–⁠372340410
Dec 28 ✦vs.Miami (OH)L 17–⁠43112125
2023 Colorado State 11 games, 15 of 19 field goals
DateOpponentResultFGMFGALongXPPts
Sep 2vs.Washington StateL 24–⁠50113836
Sep 16atColoradoL 35–⁠4301055
Sep 23atMiddle TennesseeW 31–⁠23113247
Oct 7atUtah StateL 24–⁠44113036
Oct 14vs.Boise StateW 31–⁠30124847
Oct 21atUNLVL 23–⁠253355211
Oct 28vs.Air ForceL 13–⁠30224917
Nov 3atWyomingL 15–⁠2401011
Nov 11vs.San Diego StateW 22–⁠19223428
Nov 18vs.NevadaW 30–⁠203342312
Nov 25atHawai’iL 24–⁠27122214
2022 Utah 9 games, 6 of 8 field goals
DateOpponentResultFGMFGALongXPPts
Sep 3atFloridaL 26–⁠29224328
Sep 10vs.Southern UtahW 73–⁠711261013
Sep 17vs.San Diego StateW 35–⁠700055
Sep 24atArizona StateW 34–⁠132228410
Oct 1vs.Oregon StateW 42–⁠1600066
Oct 8atUCLAL 32–⁠42122336
Oct 15vs.USCW 43–⁠4201000
Nov 19atOregonL 17–⁠2000011
Jan 2 ✦vs.Penn StateL 21–⁠3500033
2021 Utah 5 games, 2 of 4 field goals
DateOpponentResultFGMFGALongXPPts
Sep 25vs.Washington StateW 24–⁠1300022
Oct 9atUSCW 42–⁠2600066
Oct 16vs.Arizona StateW 35–⁠2100055
Oct 23atOregon StateL 34–⁠422333410
Oct 30vs.UCLAW 44–⁠2401044
2020 Utah 1 game, 1 tackle
DateOpponentResultFGMFGALongXPPts
Dec 12atColoradoW 38–⁠21–––––

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.