Kicker, Utah State, 2007–⁠09

Chris Ulinski

Number
No. 16
Height
6′3″
Hometown
Grass Valley, CA

Chris Ulinski played kicker at Utah State (2007–⁠09).

Career highs

3field goals, career highvs. Louisiana Tech, 2009

Kicking

Field goals made, season by season, with his team’s record
SeasonTeamFGMFGAPctLongXPPts
2007*Utah State00–011
2008*Utah State22100.05606
2009Utah State132161.9484079
Career152365.2564186

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. A dash: the source has no number for that season (often an FCS season), and career totals count only the numbers on file.

On the roster

SeasonTeamNo.PosHt
2007Utah State16PK
2008Utah State16PK
2009Utah State16PK6′3″

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 Utah State 12 games, 13 of 21 field goals
DateOpponentResultFGMFGALongXPPts
Sep 3atUtahL 17–⁠35122925
Sep 19atTexas A&ML 30–⁠38114236
Sep 26vs.Southern UtahW 53–⁠34113469
Oct 2atBYUL 17–⁠35112025
Oct 10atNew Mexico StateL 17–⁠20123425
Oct 17vs.NevadaL 32–⁠35114836
Oct 24vs.Louisiana TechW 23–⁠213340211
Oct 31atFresno StateL 27–⁠31242639
Nov 7atHawai’iL 36–⁠4901044
Nov 14vs.San José StateW 24–⁠9114036
Nov 20vs.Boise StateL 21–⁠5201033
Nov 28atIdahoW 52–⁠491348710
2008 Utah State 3 games, 2 of 2 field goals
DateOpponentResultFGMFGALongXPPts
Sep 6atOregonL 24–⁠66–––––
Oct 18atNevadaL 17–⁠44114203
Nov 29vs.New Mexico StateW 47–⁠2115603
2007 Utah State 2 games, 1 of 3 extra points
DateOpponentResultFGMFGALongXPPts
Aug 30vs.UNLVL 16–⁠2300011
Sep 8atWyomingL 18–⁠3200000

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.