Receiver, Western Carolina, 2018–⁠21

Daquan Patten

Number
No. 6
Height
5′6″
Weight
175 lb
Hometown
Columbia, SC

Daquan Patten played receiver at Western Carolina (2018–⁠21).

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2018Western Carolina3144.7010
2019Western Carolina177.007
2020*Western Carolina22412.0014
2021*Western Carolina166.006
Career7517.3014

Returns

SeasonTeamKRYdsTDPRYdsTD
2019Western Carolina2280–––
2021*Western Carolina–––1160
Career22801160

Defense

SeasonTeamTklSoloTFLSacksPDHur
2019Western Carolina210000

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.PosHtWt
2018Western Carolina6WR
2019Western Carolina6WR
2020Western Carolina6WR
2021Western Carolina6WR5′6″175

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
2018Western Carolina (FCS)5-0.13––-0.6–
2019Western Carolina (FCS)3-0.14––-0.4–
2020Western Carolina (FCS)20.23––0.5–
2021Western Carolina (FCS)12.05––2.1–

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

2021 Western Carolina 1 game, 1 catch, 6 yards
DateOpponentResultRecRec ydsRec TDKRYdsPR
Sep 11atOklahomaL 0–⁠76160––1

No box score in the source for Sep 4 vs. Eastern Kentucky, so that game is not listed.

2020 Western Carolina 1 game, 2 catches, 24 yards
DateOpponentResultRecRec ydsRec TDKRYdsPR
Nov 14atLibertyL 14–⁠582240–––

No box score in the source for Nov 21 at Eastern Kentucky; Feb 20 at Furman; Feb 27 at Samford; Mar 6 vs. VMI; Mar 13 vs. The Citadel; Mar 20 at Mercer; Mar 27 at East Tennessee State, so those games are not listed.

2019 Western Carolina 2 games, 1 catch, 7 yards
DateOpponentResultRecRec ydsRec TDKRYdsPR
Sep 7atNC StateL 0–⁠41–––228–
Nov 23atAlabamaL 3–⁠66170–––

No box score in the source for Aug 31 vs. Mercer; Sep 14 vs. North Greenville; Sep 28 at Chattanooga; Oct 5 vs. Gardner-Webb; Oct 12 at The Citadel; Oct 19 at Wofford; Oct 26 vs. Furman; Nov 2 at VMI; Nov 9 vs. East Tennessee State; Nov 16 vs. Samford, so those games are not listed.

2018 Western Carolina 1 game, 3 catches, 14 yards
DateOpponentResultRecRec ydsRec TDKRYdsPR
Nov 17atNorth CarolinaL 26–⁠493140–––

No box score in the source for Sep 1 vs. Newberry; Sep 14 at Gardner-Webb; Sep 22 vs. VMI; Sep 29 at Furman; Oct 6 at Samford; Oct 13 vs. Chattanooga; Oct 20 at Mercer; Oct 27 at East Tennessee State; Nov 3 vs. The Citadel; Nov 10 vs. Wofford, so those games are not listed.

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.