Defensive back, New Mexico, 2011–⁠13

Tim Foley

Number
No. 14
Height
5′7″
Hometown
Rio Rancho, NM

Tim Foley played defensive back at New Mexico (2011–⁠13).

Returns

SeasonTeamKRYdsTDPRYdsTD
2011New Mexico2350300
2012New Mexico–––9290
2013New Mexico–––7260
Career235019550

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.

Defense before 2016

SeasonGSoloAstTklPBUFF
20121226113721
2013N12871500
On file34185221

Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources, marked by season: unmarked, cfbstats.com (Open Data Commons Attribution License), its game lines summed (G: the games he has a line in); N, NCAA statistics, via octonion/football, the season’s official lines (G: games played). A dash: the source has no number for it.

On the roster

SeasonTeamNo.PosHt
2011New Mexico14DB
2012New Mexico14DB
2013New Mexico14DB5′7″

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

2013 New Mexico 4 games, 7 returns, 26 yards
DateOpponentResultKRYdsPRYdsTD
Aug 31vs.UTSAL 13–⁠21––33–
Sep 28vs.UNLVL 42–⁠56––12–
Oct 5vs.New Mexico StateW 66–⁠17––215–
Oct 12atWyomingL 31–⁠38––16–
2012 New Mexico 6 games, 9 returns, 29 yards
DateOpponentResultKRYdsPRYdsTD
Oct 20atAir ForceL 23–⁠28––115–
Oct 27vs.Fresno StateL 32–⁠49––21–
Nov 3atUNLVL 7–⁠35––16–
Nov 10vs.WyomingL 23–⁠28––32–
Nov 17vs.NevadaL 24–⁠31––14–
Nov 24atColorado StateL 20–⁠24––11–
2011 New Mexico 4 games, 5 returns, 35 yards
DateOpponentResultKRYdsPRYdsTD
Oct 29vs.Air ForceL 0–⁠42121––0
Nov 5atSan Diego StateL 7–⁠35––1−2–
Nov 12vs.UNLVW 21–⁠14––22–
Nov 19atWyomingL 10–⁠31114––0

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.