Running back, UTEP, 2006–⁠11

Leilyon Myers

Number
No. 22
Height
6′1″
Hometown
Compton, CA

Leilyon Myers played running back at UTEP (2006–⁠11).

Career highs

81rushing yards, best game on filevs. Colorado State, 20112rushing touchdowns, best game on filefour times; last vs. Tulsa, 2011

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2010UTEP512164.2651
2011UTEP1063683.51219
On file (2010–⁠11)1575843.71851

Season lines from CollegeFootballData, regular season and bowls.

On the roster

SeasonTeamNo.PosHt
2009UTEP22RB
2010UTEP22RB
2011UTEP22RB6′1″

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.

Game by game

2011 UTEP 12 games, 368 rushing yards, 12 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 3vs.Stony BrookW 31–⁠242001––
Sep 10atSMUL 17–⁠28523212––
Sep 17atNew Mexico StateW 16–⁠10165518––
Sep 24atSouth FloridaL 24–⁠52133519––
Sep 29vs.HoustonL 42–⁠49412110––
Oct 15atTulaneW 44–⁠71151119––
Oct 22vs.Colorado StateW 31–⁠171581016––
Oct 29vs.Southern MissL 13–⁠3161414––
Nov 5atRiceL 37–⁠4172229––
Nov 12vs.East CarolinaW 22–⁠17102017––
Nov 19vs.TulsaL 28–⁠57830211––
Nov 25atUCFL 14–⁠3192505––
2010 UTEP 13 games, 216 rushing yards, 6 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 4vs.Arkansas–Pine BluffW 31–⁠1052201217
Sep 10atHoustonL 24–⁠54120218
Sep 18vs.New Mexico StateW 42–⁠10733022––
Sep 25vs.MemphisW 16–⁠132606––
Oct 2atNew MexicoW 38–⁠20103019––
Oct 9vs.RiceW 44–⁠2461929––
Oct 16atUABL 6–⁠213703––
Oct 23vs.TulaneL 24–⁠342513––
Oct 30atMarshallL 12–⁠16––––––
Nov 6vs.SMUW 28–⁠1461514––
Nov 13atArkansasL 21–⁠58671151––
Nov 20atTulsaL 28–⁠312303––
Dec 18 ✦vs.BYUL 24–⁠521303––

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.