Tight end, East Carolina (from Oklahoma), 2017–⁠22

Ryan Jones

Number
No. 4
Height
6′3″
Weight
247 lb
Class (2022)
Senior
Hometown
Charlotte, NC
Born
Aug 20, 1999

Ryan Jones played tight end at Oklahoma (2017–⁠19) and East Carolina (2021–⁠22).

Career highs

6catches, career highthree times; last vs. South Florida, 2022102receiving yards, career highvs. Temple, 20212receiving touchdowns, career highvs. Temple, 20218tackles, career highvs. Army, 2018

Team titles: Big 12 champions, 2018 and 2019

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2021East Carolina3744211.9538
2022East Carolina4141310.1425
Career7885511.0938

Defense

SeasonTeamTklSoloTFLSacksIntPDHur
2018Oklahoma20132.50001
2019Oklahoma9800101
2022East Carolina2000000
Career31212.50102

Season lines from CollegeFootballData, regular season and bowls. 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.PosClassHtWt
2018Oklahoma4TEYr 1
2019Oklahoma4TEYr 2
2021East Carolina4TEYr 4
2022East Carolina4TESr. (Yr 5)6′3″247

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
2021East Carolina390.8372nd (n=410)0.6732.46%
2022East Carolina330.7354th (n=683)0.7124.15%

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 East Carolina 11 games, 41 catches, 413 yards, 4 TD
DateOpponentResultRecRec ydsRec TDTklSacksIntPD
Sep 3vs.NC StateL 20–⁠214220––––
Sep 10vs.Old DominionW 39–⁠213391––––
Sep 17vs.CampbellW 49–⁠1031011000
Sep 24vs.NavyL 20–⁠234481––––
Oct 1vs.South FloridaW 48–⁠2868411000
Oct 8atTulaneL 9–⁠245470––––
Oct 15vs.MemphisW 47–⁠454540––––
Oct 22vs.UCFW 34–⁠134400––––
Oct 28atBYUW 27–⁠242180––––
Nov 11atCincinnatiL 25–⁠274320––––
Nov 19vs.HoustonL 3–⁠422190––––
2021 East Carolina 9 games, 37 catches, 442 yards, 5 TD
DateOpponentResultRecRec ydsRec TDTklSacksIntPD
Sep 2atApp StateL 19–⁠331381––––
Oct 2vs.TulaneW 52–⁠296581––––
Oct 9atUCFL 16–⁠204210––––
Oct 23atHoustonL 24–⁠314260––––
Oct 28vs.South FloridaW 29–⁠142150––––
Nov 6vs.TempleW 45–⁠361022––––
Nov 13atMemphisW 30–⁠294700––––
Nov 20atNavyW 38–⁠355421––––
Nov 26vs.CincinnatiL 13–⁠355700––––
2019 Oklahoma 6 games, 9 tackles, 1 INT
DateOpponentResultRecRec ydsRec TDTklSacksIntPD
Sep 1vs.HoustonW 49–⁠31–––4000
Sep 7vs.South DakotaW 70–⁠14–––0000
Sep 14atUCLAW 48–⁠14–––1010
Sep 28vs.Texas TechW 55–⁠16–––1000
Oct 5atKansasW 45–⁠20–––1000
Oct 26atKansas StateL 41–⁠48–––2000
2018 Oklahoma 6 games, 20 tackles
DateOpponentResultRecRec ydsRec TDTklSacksIntPD
Sep 1vs.Florida AtlanticW 63–⁠14–––2000
Sep 8vs.UCLAW 49–⁠21–––6000
Sep 22vs.ArmyW 28–⁠21–––8000
Oct 20atTCUW 52–⁠27–––1000
Oct 27vs.Kansas StateW 51–⁠14–––2000
Nov 3atTexas TechW 51–⁠46–––1000

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.