Running back, Tulsa, 2003–⁠06

Brandon Diles

Hometown
Abilene, TX

Brandon Diles played running back at Tulsa (2003–⁠06).

At a glance

Best season
597
Rushing yards, 2004 (Tulsa, 4–⁠8)
Best game
202 yards
At Nevada, week 9, 2004: No. 2 rushing game in FBS that week

Career highs

202rushing yards, career highat Nevada, 20043rushing touchdowns, career highat Nevada, 20046catches, career highat Navy, 2006

Team titles: Conference USA champions, 2005

Rushing

Rushing yards, season by season, with his team’s record
SeasonTeamCarYdsAvgTDLong
2004Tulsa1245974.8743
2005Tulsa402476.2341
2006Tulsa643014.7326
Career2281,1455.01343

Receiving

SeasonTeamRecYdsAvgTDLong
2004Tulsa45914.8135
2006Tulsa1111410.4039
Career1517311.5139

Season lines from CollegeFootballData, regular season and bowls. Every season here is summed from the game box scores (the source has no season lines for them; a game missing from the box scores is missing here).

Game by game

2006 Tulsa 6 games, 301 rushing yards, 3 TD
DateOpponentResultCarYdsTDLongRecRec yds
Aug 31vs.Stephen F. AustinW 45–⁠71461021111
Sep 9atBYUL 24–⁠498170619
Sep 16vs.North TexasW 28–⁠3847214255
Sep 23atNavyW 24–⁠231590026629
Oct 27vs.UTEPW 30–⁠20647014––
Nov 24vs.TulaneW 38–⁠3133917110
2005 Tulsa 5 games, 247 rushing yards, 3 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 10atOklahomaL 15–⁠31419014––
Sep 17atNorth TexasW 54–⁠215128141––
Sep 24vs.MemphisW 37–⁠3193518––
Oct 15atRiceW 41–⁠213703––
Nov 5atUTEPL 38–⁠41958114––
2004 Tulsa 11 games, 597 rushing yards, 7 TD
DateOpponentResultCarYdsTDLongRecRec yds
Sep 4atKansasL 3–⁠211707––
Sep 11atOklahoma StateL 21–⁠38212111––
Sep 18vs.NavyL 0–⁠2961205––
Sep 25vs.Missouri StateW 49–⁠71079022––
Oct 16vs.Boise StateL 42–⁠451551010117
Oct 23atNevadaL 48–⁠543420232214
Oct 30vs.RiceW 39–⁠221892043––
Nov 6atSMUL 35–⁠4182901713
Nov 13atLouisiana TechL 21–⁠3882819––
Nov 20vs.San José StateW 34–⁠24844013135
Nov 27vs.UTEPW 37–⁠35144128––

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.