Receiver, Colorado, 2018–⁠22

Daniel Arias

Number
No. 6
Height
6′4″
Weight
210 lb
Class (2022)
Senior
Hometown
Mill Creek, WA
Born
Sep 2, 1998

Daniel Arias played receiver at Colorado (2018–⁠22).

Career highs

82receiving yards, career highvs. UCLA, 2022

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2018Colorado13737.0137
2019Colorado36220.7129
2020Colorado610517.5038
2021Colorado1923712.5143
2022Colorado1930916.3142
Career4875015.6443

Defense

SeasonTeamTklSoloTFLSacksPDHur
2018Colorado210000
2019Colorado220000
2022Colorado430000
Career860000

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2018Colorado6WRYr 1
2019Colorado6WRYr 2
2020Colorado6WRYr 3
2021Colorado6WRYr 4
2022Colorado6WRSr. (Yr 5)6′4″210

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
2018Colorado30.98––2.9–
2019Colorado50.92––4.6–
2020Colorado140.55––7.7–
2021Colorado240.84––20.14%
2022Colorado191.06––20.2–

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

2022 Colorado 9 games, 19 catches, 309 yards, 1 TD
DateOpponentResultRecRec ydsRec TDTklSacksPD
Sep 2vs.TCUL 13–⁠384660–––
Sep 10atAir ForceL 10–⁠412360100
Sep 17atMinnesotaL 7–⁠493220–––
Sep 24vs.UCLAL 17–⁠454820–––
Oct 1atArizonaL 20–⁠433311–––
Oct 15vs.CaliforniaW 20–⁠132580–––
Oct 22atOregon StateL 9–⁠421140–––
Oct 29vs.Arizona StateL 34–⁠42–––200
Nov 11atUSCL 17–⁠55–––100
2021 Colorado 10 games, 19 catches, 237 yards, 1 TD
DateOpponentResultRecRec ydsRec TDTklSacksPD
Sep 11vs.Texas A&ML 7–⁠103370–––
Sep 18vs.MinnesotaL 0–⁠30180–––
Oct 2vs.USCL 14–⁠371180–––
Oct 16vs.ArizonaW 34–⁠02120–––
Oct 23atCaliforniaL 3–⁠26180–––
Oct 30atOregonL 29–⁠52110–––
Nov 6vs.Oregon StateW 37–⁠342521–––
Nov 13atUCLAL 20–⁠444700–––
Nov 20vs.WashingtonW 20–⁠173220–––
Nov 26atUtahL 13–⁠28190–––
2020 Colorado 5 games, 6 catches, 105 yards
DateOpponentResultRecRec ydsRec TDTklSacksPD
Nov 7vs.UCLAW 48–⁠421380–––
Nov 14atStanfordW 35–⁠321100–––
Dec 5atArizonaW 24–⁠13170–––
Dec 12vs.UtahL 21–⁠382330–––
Dec 29 ✦vs.TexasL 23–⁠551170–––
2019 Colorado 4 games, 3 catches, 62 yards, 1 TD
DateOpponentResultRecRec ydsRec TDTklSacksPD
Sep 14vs.Air ForceL 23–⁠30–––100
Oct 5vs.ArizonaL 30–⁠352350–––
Oct 25vs.USCL 31–⁠35–––100
Nov 30atUtahL 15–⁠451271–––
2018 Colorado 3 games, 1 catch, 37 yards, 1 TD
DateOpponentResultRecRec ydsRec TDTklSacksPD
Oct 13atUSCL 20–⁠31–––100
Oct 20atWashingtonL 13–⁠271371–––
Nov 2atArizonaL 34–⁠42–––100

Box scores from CollegeFootballData, 2004 on. ✦ postseason; ★ a career high on file.

Before the draft

DrillPro day 2023
Height6′3½″
Weight208 lb
Arm length33¼″
Hand size9″
40-yard dash4.52 s
10-yard split1.58 s
Vertical jump38″
Broad jump10′7″
Bench press9 reps
3-cone drill7.09 s
20-yard shuttle4.27 s

Pre-draft measurables: Wikipedia (CC BY-SA).

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.