Receiver, Tarleton State (from Utah Tech), 2023–⁠26

Bryce Parker

Number
No. 10
Height
5′9″
Weight
180 lb
Class (2026)
Senior
Hometown
Corona, CA

Bryce Parker plays receiver for Tarleton State, after Utah Tech (2023–⁠24). Last time out, against Chicago State: 1 catch, 23 yards, 1 TD.

2026 so far

10 catches, 140 yards, 1 TD

Last game: 1 catch, 23 yards, 1 TD vs. Chicago State, W 56–⁠21

Next game: at West Georgia, Oct 24

Game by game this season, receiving yards
  1. 89@MCN
  2. 28MRMK
  3. 23Chica

Filled bars: wins; outlined: losses.

Career highs

7catches, career highat McNeese, 202698receiving yards, career highat North Alabama, 20242receiving touchdowns, career highvs. Mississippi Valley State, 2025

Team titles: United Athletic champions, 2025

Receiving

Receiving yards, season by season, with his team’s record

* The season in progress, so far.

SeasonTeamRecYdsAvgTDLong
2023*Utah Tech166.006
2024Utah Tech2538815.5475
2025Tarleton State1324018.5334
2026Tarleton State1014014.0138
Career4977415.8875

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.

On the roster

SeasonTeamNo.PosClassHtWt
2023Utah Tech10WRFr.
2024Utah Tech10WRSo.
2025Tarleton State10WRJr.
2026Tarleton State10WRSr.5′9″180

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/playPctileMedianTotalUsage
2025Tarleton State (FCS)250.67––16.83%
2026Tarleton State (FCS)160.49––7.9–

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). From CollegeFootballData, 2013 on.

Game by game

2026 Tarleton State 3 games, 10 catches, 140 yards, 1 TD
DateOpponentResultRecYdsTDLongRush
Sep 12atMcNeeseW 27–⁠24789038–
Sep 19vs.MerrimackW 45–⁠20228020–
Oct 3vs.Chicago StateW 56–⁠21123123–
2025 Tarleton State 9 games, 13 catches, 240 yards, 3 TD
DateOpponentResultRecYdsTDLongRush
Sep 6vs.Mississippi Valley StateW 59–⁠3238221–
Sep 13atCentral ArkansasW 56–⁠101808–
Sep 20vs.ChattanoogaW 52–⁠24360032–
Oct 4vs.Southern UtahW 52–⁠42112012–
Oct 11atUtah TechW 41–⁠231000–
Oct 18vs.West GeorgiaW 45–⁠10124024–
Oct 25atEastern KentuckyW 31–⁠7128028–
Nov 1atAbilene ChristianL 28–⁠31110010–
Nov 15vs.North AlabamaW 61–⁠0260134–
2024 Utah Tech 11 games, 25 catches, 388 yards, 4 TD
DateOpponentResultRecYdsTDLongRush
Aug 31vs.Montana StateL 7–⁠311707–
Sep 7atUNLVL 14–⁠723520371
Sep 21atUC DavisL 14–⁠3226514815
Sep 28vs.Abilene ChristianL 30–⁠55341016–
Oct 5atNorth AlabamaL 14–⁠60398175–
Oct 12atTarleton StateL 0–⁠42221017–
Oct 19vs.Austin PeayL 7–⁠13216012–
Oct 26atEastern KentuckyL 17–⁠281919–
Nov 2vs.Central ArkansasW 34–⁠21112012–
Nov 16vs.West GeorgiaL 31–⁠34329113–
Nov 23atSouthern UtahL 34–⁠37438016–
2023 Utah Tech 1 game, 1 catch, 6 yards
DateOpponentResultRecYdsTDLongRush
Sep 23atMissouri StateL 14–⁠591606–

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.