Running back, Tulane, 2012–⁠16

Lazedrick Thompson

Number
No. 33
Height
5′11″
Hometown
LaPlace, LA

Lazedrick Thompson played running back at Tulane (2012–⁠16).

Career highs

124rushing yards, career highat Duke, 20143rushing touchdowns, career highat UConn, 2016

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2013Tulane22683.1016
2014Tulane1095334.9448
2015Tulane451623.6115
2016*Tulane875065.8745
Career2631,2694.81248

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.

On the roster

SeasonTeamNo.PosHt
2012Tulane33RB
2013Tulane33RB
2014Tulane33RB
2015Tulane33RB
2016Tulane33RB5′11″

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/playPctileMedianTotalUsageAdj. rush
2013Tulane120.03––0.3––
2014Tulane1100.1251st (n=253)0.1213.615%0.25
2015Tulane44-0.03––-1.18%0.02
2016Tulane900.4197th (n=259)0.1336.611%0.37

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). Adjusted pass and rush: EPA per play adjusted for the defenses faced (CollegeFootballData’s WEPA). From CollegeFootballData, 2013 on.

Game by game

2016 Tulane 12 games, 506 rushing yards, 7 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 1atWake ForestL 3–⁠76210816
Sep 10vs.SouthernW 66–⁠21428211––
Sep 17vs.NavyL 14–⁠2162008––
Sep 24vs.LouisianaW 41–⁠3973008––
Oct 1atMassachusettsW 31–⁠24854119––
Oct 14vs.MemphisL 14–⁠248690361−6
Oct 22atTulsaL 27–⁠50766141––
Oct 29vs.SMUL 31–⁠353804––
Nov 5atUCFL 6–⁠37960026––
Nov 12atHoustonL 18–⁠30220016––
Nov 19vs.TempleL 0–⁠3142208––
Nov 26atUConnW 38–⁠1323108345––
2015 Tulane 8 games, 162 rushing yards, 1 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 3vs.DukeL 7–⁠3761205––
Sep 12atGeorgia TechL 10–⁠651374015––
Sep 19vs.MaineW 38–⁠71346111––
Oct 3vs.UCFW 45–⁠311101––
Nov 7vs.UConnL 3–⁠72−401––
Nov 14atArmyW 34–⁠3151309––
Nov 21atSMUL 21–⁠492905––
Nov 27vs.TulsaL 34–⁠4531105––
2014 Tulane 10 games, 533 rushing yards, 4 TD
DateOpponentResultCarYdsTDLongRecRec yds
Aug 28atTulsaL 31–⁠3851106––
Sep 6vs.Georgia TechL 21–⁠3882908––
Sep 13vs.SE LouisianaW 35–⁠20133018––
Sep 20atDukeL 13–⁠471912411514
Sep 27atRutgersL 6–⁠3183109––
Oct 11vs.UConnW 12–⁠31273024––
Oct 18atUCFL 13–⁠201263121––
Oct 31vs.CincinnatiL 14–⁠38939119––
Nov 15vs.MemphisL 7–⁠381270016––
Dec 6vs.TempleL 3–⁠101163048––
2013 Tulane 8 games, 68 rushing yards
DateOpponentResultCarYdsTDLongRecRec yds
Aug 29vs.Jackson StateW 34–⁠771907––
Sep 7vs.South AlabamaL 39–⁠411101––
Sep 12atLouisiana TechW 24–⁠15––––131
Sep 21atSyracuseL 17–⁠522804––
Sep 28atUL MonroeW 31–⁠145603––
Oct 5vs.North TexasW 24–⁠211000––
Oct 12vs.East CarolinaW 36–⁠33522016––
Oct 26vs.TulsaW 14–⁠7112012––

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.