Kicker, Texas Tech, 2014–⁠18

Clayton Hatfield

Number
No. 96
Height
5′10″
Weight
185 lb
Class (2018)
Senior
Hometown
Boerne, TX

Clayton Hatfield played kicker at Texas Tech (2014–⁠18).

Career highs

3field goals, career highat Kansas, 2015

Honors

Kicking

Field goals made, season by season, with his team’s record
SeasonTeamFGMFGAPctLongXPPts
2015Texas Tech141687.5515395
2016Texas Tech131492.94365104
2017Texas Tech61060.0392240
2018Texas Tech171989.54855106
Career505984.751195345

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2014Texas Tech96PKRS
2015Texas Tech96PKFr.
2016Texas Tech96PKSo.
2017Texas Tech96PKJr.
2018Texas Tech96PKSr.5′10″185

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
2016Texas Tech––––––6.1 (14 att.)
2017Texas Tech––––––-5.9 (10 att.)
2018Texas Tech––––––6.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

2018 Texas Tech 12 games, 17 of 19 field goals
DateOpponentResultFGMFGALongXPPts
Sep 1vs.Ole MissL 27–⁠47224139
Sep 8vs.LamarW 77–⁠00001111
Sep 15vs.HoustonW 63–⁠4900099
Sep 22atOklahoma StateW 41–⁠172332511
Sep 29vs.West VirginiaL 34–⁠422227410
Oct 11atTCUW 17–⁠14112225
Oct 20vs.KansasW 48–⁠162248612
Oct 27atIowa StateL 31–⁠40112747
Nov 3vs.OklahomaL 46–⁠512243410
Nov 10vs.TexasL 34–⁠412241410
Nov 17atKansas StateL 6–⁠21224206
Nov 24vs.BaylorL 24–⁠35124236
2017 Texas Tech 6 games, 6 of 10 field goals
DateOpponentResultFGMFGALongXPPts
Sep 16vs.Arizona StateW 52–⁠4500055
Nov 4vs.Kansas StateL 35–⁠4201055
Nov 11vs.BaylorW 38–⁠24113958
Nov 18vs.TCUL 3–⁠27132203
Nov 24atTexasW 27–⁠23233439
Dec 23 ✦vs.South FloridaL 34–⁠382233410
2016 Texas Tech 12 games, 13 of 14 field goals
DateOpponentResultFGMFGALongXPPts
Sep 3vs.Stephen F. AustinW 69–⁠172243915
Sep 10atArizona StateL 55–⁠6800077
Sep 17vs.Louisiana TechW 59–⁠451224811
Sep 29vs.KansasW 55–⁠1900077
Oct 8atKansas StateL 38–⁠44113458
Oct 15vs.West VirginiaL 17–⁠48114225
Oct 22vs.OklahomaL 59–⁠661137811
Oct 29atTCUW 27–⁠24224139
Nov 5vs.TexasL 37–⁠45114247
Nov 12atOklahoma StateL 44–⁠45112758
Nov 19atIowa StateL 10–⁠66113114
Nov 25vs.BaylorW 54–⁠352231612
2015 Texas Tech 12 games, 14 of 16 field goals
DateOpponentResultFGMFGALongXPPts
Sep 5vs.Sam HoustonW 59–⁠4500011
Sep 12vs.UTEPW 69–⁠20113325
Sep 26vs.TCUL 52–⁠551137710
Oct 3vs.BaylorL 35–⁠6300055
Oct 10vs.Iowa StateW 66–⁠311124912
Oct 17atKansasW 30–⁠203430110
Oct 24atOklahomaL 27–⁠63223439
Oct 31vs.Oklahoma StateL 53–⁠70114269
Nov 7atWest VirginiaL 26–⁠31223428
Nov 14vs.Kansas StateW 59–⁠441248811
Nov 26atTexasW 48–⁠452251612
Dec 29 ✦vs.LSUL 27–⁠5600033

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.