Tight end, Tulane, 2018–⁠22

Tyrick James

Number
No. 80
Height
6′2″
Weight
245 lb
Class (2022)
Senior
Hometown
Waco, TX

Tyrick James played tight end at Tulane (2018–⁠22).

Career highs

6catches, career highat Oklahoma, 202193receiving yards, career highat Oklahoma, 2021

Team titles: American champions, 2022

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2018Tulane3196.309
2019Tulane1928314.9145
2020Tulane1820211.2329
2021Tulane3142913.8443
2022Tulane2528511.4529
Career961,21812.71345

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosClassHtWt
2018Tulane80TEYr 1
2019Tulane80TEYr 2
2020Tulane80TEYr 3
2021Tulane80TEYr 4
2022Tulane80TESr. (Yr 5)6′2″245

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
2018Tulane30.09––0.3–
2019Tulane240.86––20.74%
2020Tulane250.69––17.24%
2021Tulane291.06––30.85%
2022Tulane310.9480th (n=683)0.7129.34%

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 Tulane 11 games, 25 catches, 285 yards, 5 TD
DateOpponentResultRecYdsTDLongRush
Sep 10vs.Alcorn StateW 52–⁠0251126–
Sep 17atKansas StateW 17–⁠1021117–
Sep 30atHoustonW 27–⁠242714–
Oct 8vs.East CarolinaW 24–⁠9332125–
Oct 15atSouth FloridaW 45–⁠315790293
Oct 22vs.MemphisW 38–⁠28226016–
Nov 5atTulsaW 27–⁠13439119–
Nov 12vs.UCFL 31–⁠38110010–
Nov 17vs.SMUW 59–⁠2421207–
Nov 25atCincinnatiW 27–⁠241−100–
Dec 3vs.UCFW 45–⁠28119019–
2021 Tulane 11 games, 31 catches, 429 yards, 4 TD
DateOpponentResultRecYdsTDLongRush
Sep 4atOklahomaL 35–⁠40693043–
Sep 11vs.Morgan StateW 69–⁠20249143–
Sep 18atOle MissL 21–⁠61347122–
Sep 25vs.UABL 21–⁠28457029–
Oct 2atEast CarolinaL 29–⁠52443019–
Oct 7vs.HoustonL 22–⁠40354134–
Oct 21atSMUL 26–⁠551707–
Oct 30vs.CincinnatiL 12–⁠311808–
Nov 6atUCFL 10–⁠14322011–
Nov 20vs.South FloridaW 45–⁠14130130–
Nov 27atMemphisL 28–⁠33319017–
2020 Tulane 10 games, 18 catches, 202 yards, 3 TD
DateOpponentResultRecYdsTDLongRush
Sep 12atSouth AlabamaW 27–⁠24123023–
Sep 19vs.NavyL 24–⁠27238029–
Oct 8atHoustonL 31–⁠491808–
Oct 16vs.SMUL 34–⁠37219013–
Oct 24atUCFL 34–⁠5114040
Nov 7atEast CarolinaW 38–⁠21218113–
Nov 14vs.ArmyW 38–⁠1221218–
Nov 19atTulsaL 24–⁠30219119–
Dec 5vs.MemphisW 35–⁠21330016–
Dec 22 ✦vs.NevadaL 27–⁠38231022–
2019 Tulane 7 games, 19 catches, 283 yards, 1 TD
DateOpponentResultRecYdsTDLongRush
Aug 29vs.Florida InternationalW 42–⁠14460118–
Oct 12vs.UConnW 49–⁠7251039–
Oct 19atMemphisL 17–⁠47–––––
Oct 26atNavyL 38–⁠41145045–
Nov 16atTempleL 21–⁠29434016–
Nov 23vs.UCFL 31–⁠34331018–
Nov 30atSMUL 20–⁠37562017–
2018 Tulane 4 games, 3 catches, 19 yards
DateOpponentResultRecYdsTDLongRush
Aug 30vs.Wake ForestL 17–⁠231505–
Oct 6atCincinnatiL 21–⁠3721409–
Oct 20vs.SMUL 23–⁠27–––––
Nov 15atHoustonL 17–⁠48–––––

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.