Receiver, Nevada, 2005–⁠07

Kyle Sammons

Hometown
Novato, CA

Kyle Sammons played receiver at Nevada (2005–⁠07).

At a glance

Best season
623
Receiving yards, 2007 (Nevada, 6–⁠7)
Best game
199 yards
Vs. Louisiana Tech, week 14, 2007: No. 2 receiving game in FBS that week

Career highs

8catches, career highvs. Louisiana Tech, 2007199receiving yards, career highvs. Louisiana Tech, 20072receiving touchdowns, career highvs. Louisiana Tech, 2007

Team titles: WAC champions, 2005

Receiving

Receiving yards, season by season, with his team’s record
SeasonTeamRecYdsAvgTDLong
2005Nevada2737513.9252
2007‡Nevada3362318.9474
Career6099816.6674

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). ‡ Short by one game in 2007 (Nov 24 at San José State): the source has no box score for it.

Game by game

2007 Nevada 11 games, 33 catches, 623 yards, 4 TD
DateOpponentResultRecYdsTDLong
Sep 1atNebraskaL 10–⁠52119019
Sep 8atNorthwesternL 31–⁠365102148
Sep 15vs.NichollsW 52–⁠17131031
Sep 29vs.UNLVW 27–⁠20364143
Oct 6vs.Fresno StateL 41–⁠49569020
Oct 14atBoise StateL 67–⁠69111011
Oct 27vs.IdahoW 37–⁠21569023
Nov 2atNew Mexico StateW 40–⁠38118018
Nov 16vs.Hawai’iL 26–⁠28232026
Dec 1vs.Louisiana TechW 49–⁠108199274
Dec 22 ✦vs.New MexicoL 0–⁠231909

No box score in the source for Nov 24 at San José State, so that game is not listed.

2005 Nevada 11 games, 27 catches, 375 yards, 2 TD
DateOpponentResultRecYdsTDLong
Sep 9vs.Washington StateL 21–⁠55120020
Sep 24atColorado StateL 21–⁠427103143
Oct 1atSan José StateW 30–⁠23344123
Oct 8vs.IdahoW 62–⁠14115015
Oct 15vs.Louisiana TechW 37–⁠27668027
Oct 29atBoise StateL 14–⁠4921508
Nov 5vs.Hawai’iW 38–⁠281505
Nov 12atNew Mexico StateW 48–⁠24114014
Nov 19atUtah StateW 30–⁠24224015
Nov 26vs.Fresno StateW 38–⁠35259052
Dec 24 ✦vs.UCFW 49–⁠481808

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.