Kicker, San José State, 2015–⁠18

Bryce Crawford

Number
No. 38
Height
6′3″
Weight
244 lb
Class (2018)
Senior
Hometown
Frisco, TX

Bryce Crawford played kicker at San José State (2015–⁠18).

Career highs

3field goals, career highsix times; last vs. UNLV, 2018

Kicking

Field goals made, season by season, with his team’s record
SeasonTeamFGMFGAPctLongXPPts
2015San José State1250.03869
2016San José State161888.9443179
2017San José State141782.4532062
2018San José State141973.7502567
Career455680.45382217

Punting

SeasonTeamPuntsYdsAvgLongIn 20
2017San José State1039739.7480
2018San José State652,87044.26117
Career753,26743.66117

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2015San José State38PKFr.
2016San José State38PKSo.
2017San José State38PKJr.
2018San José State38PKSr.6′3″244

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
2016San José State––––––3.8 (18 att.)
2017San José State––––––10.6 (17 att.)
2018San José State––––––0.2 (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 San José State 12 games, 14 of 19 field goals
DateOpponentResultFGMFGALongXPPts
Aug 30vs.UC DavisL 38–⁠44122958
Sep 8atWashington StateL 0–⁠31–––––
Sep 15atOregonL 22–⁠353331110
Sep 29vs.Hawai’iL 41–⁠442624511
Oct 6vs.Colorado StateL 30–⁠4200044
Oct 13vs.ArmyL 3–⁠52114903
Oct 20atSan Diego StateL 13–⁠16224217
Oct 27vs.UNLVW 50–⁠373350514
Nov 3atWyomingL 9–⁠24112603
Nov 10atUtah StateL 24–⁠62112836
Nov 17vs.NevadaL 12–⁠2100000
Nov 24atFresno StateL 13–⁠3100011
2017 San José State 12 games, 14 of 17 field goals
DateOpponentResultFGMFGALongXPPts
Aug 26vs.South FloridaL 22–⁠42113414
Sep 2vs.Cal PolyW 34–⁠1300044
Sep 16atUtahL 16–⁠543351110
Sep 23vs.Utah StateL 10–⁠61115314
Sep 30atUNLVL 13–⁠41232817
Oct 7vs.Fresno StateL 10–⁠27115114
Oct 14atHawai’iL 26–⁠37235228
Oct 28atBYUL 20–⁠41224828
Nov 4vs.San Diego StateL 7–⁠5200011
Nov 11atNevadaL 14–⁠5900022
Nov 18atColorado StateL 14–⁠4200022
Nov 25vs.WyomingW 20–⁠17235228
2016 San José State 12 games, 16 of 18 field goals
DateOpponentResultFGMFGALongXPPts
Sep 3atTulsaL 10–⁠45113614
Sep 10vs.Portland StateW 66–⁠351122912
Sep 17vs.UtahL 17–⁠34112925
Sep 24atIowa StateL 10–⁠44112214
Oct 1atNew MexicoL 41–⁠4801055
Oct 8vs.Hawai’iL 17–⁠34122025
Oct 15vs.NevadaW 14–⁠1000022
Oct 21atSan Diego StateL 3–⁠42112603
Oct 29vs.UNLVW 30–⁠243344312
Nov 4atBoise StateL 31–⁠453339211
Nov 19vs.Air ForceL 38–⁠41113136
Nov 26atFresno StateW 16–⁠143328110
2015 San José State 3 games, 1 of 2 field goals
DateOpponentResultFGMFGALongXPPts
Sep 3vs.New HampshireW 43–⁠13113825
Sep 12atAir ForceL 16–⁠3701011
Oct 3atAuburnL 21–⁠3500033

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.