Receiver, North Carolina A&T, 2024–⁠26

Jayvonne Dillard

Number
No. 5
Height
6′2″
Weight
205 lb
Class (2026)
Junior
Hometown
Lithonia, GA

Jayvonne Dillard plays receiver for North Carolina A&T. Last time out, against Chicago State: 2 catches, 47 yards.

2026 so far

18 catches, 254 yards

Last game: 2 catches, 47 yards vs. Chicago State, W 27–⁠12

Next game: vs. Elon, Oct 31

Game by game this season, receiving yards
  1. 50MORG
  2. 32@GAST
  3. 47@NCCU
  4. 13@CAM
  5. 39URI
  6. 8@BRY
  7. 18UNH
  8. 47Chica

Filled bars: wins; outlined: losses.

Career highs

6catches, career highthree times; last vs. Monmouth, 2025103receiving yards, career highvs. Monmouth, 2025

Receiving

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

* The season in progress, so far.

SeasonTeamRecYdsAvgTDLong
2024North Carolina A&T3238612.1043
2025North Carolina A&T4353912.5249
2026North Carolina A&T1825414.1030
Career931,17912.7249

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2024North Carolina A&T5WRFr.
2025North Carolina A&T5WRSo.
2026North Carolina A&T5WRJr.6′2″205

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
2025North Carolina A&T (FCS)650.4245th (n=1040)0.4627.610%
2026North Carolina A&T (FCS)370.2627th (n=829)0.439.87%

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 North Carolina A&T 8 games, 18 catches, 254 yards
DateOpponentResultRecYdsTDLongRush
Aug 29vs.Morgan StateL 7–⁠17350020–
Sep 4atGeorgia StateL 10–⁠59332017–
Sep 12atNorth Carolina CentralL 22–⁠30347019–
Sep 19atCampbellL 14–⁠42213012–
Sep 26vs.Rhode IslandW 22–⁠18339024–
Oct 3atBryantL 30–⁠311808–
Oct 10vs.New HampshireW 30–⁠27118018–
Oct 17vs.Chicago StateW 27–⁠12247030–
2025 North Carolina A&T 11 games, 43 catches, 539 yards, 2 TD
DateOpponentResultRecYdsTDLongRush
Aug 30atTennessee StateL 21–⁠2436010–
Sep 13vs.HamptonW 33–⁠30559042–
Sep 20vs.North Carolina CentralL 20–⁠62334016–
Sep 27atMaineL 30–⁠37670134–
Oct 4atWilliam & MaryL 34–⁠38672116–
Oct 11vs.South Carolina StateL 16–⁠22239030–
Oct 25vs.CampbellW 28–⁠24372049–
Nov 1vs.TowsonL 9–⁠62543013–
Nov 8atStony BrookL 12–⁠38225013–
Nov 15vs.MonmouthL 19–⁠636103029–
Nov 22atElonL 17–⁠5521609–
2024 North Carolina A&T 11 games, 32 catches, 386 yards
DateOpponentResultRecYdsTDLongRush
Aug 29atWake ForestL 13–⁠45231027–
Sep 7vs.Winston-Salem StateW 27–⁠20328013–
Sep 14vs.DelawareL 13–⁠42571019–
Sep 21atNorth Carolina CentralL 24–⁠66323011–
Sep 28atSouth Carolina StateL 25–⁠453680438
Oct 5atRichmondL 17–⁠20311011–
Oct 19vs.HamptonL 17–⁠59234029–
Oct 26atCampbellL 7–⁠213390228
Nov 9atVillanovaL 3–⁠31219011–
Nov 16atTowsonL 13–⁠31437018–
Nov 23vs.ElonL 21–⁠31225013–

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.