Cornerback, Washington State, 2008–⁠12

Daniel Simmons

Number
No. 24
Height
5′10″
Hometown
Ontario, CA

Daniel Simmons played cornerback at Washington State (2008–⁠12).

Defense

SeasonTeamInt
2012Washington State2

Season lines from CollegeFootballData, regular season and bowls. Before 2016 our source records only interceptions for most defenders (no tackles, tackles for loss or sacks), so these lines count interceptions only. His tackles, tackles for loss and sacks from other sources are under “Defense before 2016” below.

Defense before 2016

SeasonGSoloAstTklTFLIntPBUHur
20096183212021
20108236292030
2011N10221231–3–
20129365413.5260
On file99151148.5–14–

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
2009Washington State24CB
2010Washington State24CB
2011Washington State24CB
2012Washington State24CB5′10″

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

2012 Washington State 2 games with an interception on file, 2 INT
DateOpponentResultInt
Sep 22vs.ColoradoL 34–⁠351
Nov 17atArizona StateL 7–⁠461
2009 Washington State 0 games with an interception on file, 3 returns, 75 yards
DateOpponentResultInt

Box scores from CollegeFootballData, 2004 on. ✦ postseason; ★ a career high on file. Before 2016 our source’s box scores record only interceptions for defenders (no tackles, tackles for loss or sacks), so only those games are listed. His tackles, tackles for loss and sacks from other sources are under “Defense before 2016” below.

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.