Safety, San José State, 2010–⁠13

Damon Ogburn Jr.

Number
No. 6
Height
5′11″
Weight
181 lb
Hometown
San Bernardino, CA

Damon Ogburn Jr. played safety at San José State (2010–⁠13).

Returns

SeasonTeamKRYdsTDPRYdsTD
2012San José State51270–––
2013San José State152560280
Career203830280

Defense

SeasonTeamInt
2012San José State1

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). 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

SeasonGSoloAstTklTFLSacksIntPBUFF
2010635800000
20118941300000
20128268340.50.5113
On file3817550.50.5113

Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources: cfbstats.com (Open Data Commons Attribution License), its game lines summed (G: the games he has a line in). A dash: the source has no number for it.

On the roster

SeasonTeamNo.PosHtWt
2010San José State6CB
2011San José State6CB
2012San José State6CB
2013San José State6S5′11″181

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 San José State 6 games, 17 returns, 264 yards
DateOpponentResultKRYdsPRYdsTD
Sep 7atStanfordL 13–⁠34357––0
Sep 21atMinnesotaL 24–⁠43583––0
Sep 27vs.Utah StateL 12–⁠40359––0
Oct 12atColorado StateW 34–⁠27232––0
Oct 26vs.WyomingW 51–⁠44––28–
Nov 9vs.San Diego StateL 30–⁠34225––0
2012 San José State 4 games, 1 INT
DateOpponentResultKRYdsPRYdsTD
Sep 22atSan Diego StateW 38–⁠34286––0
Sep 29atNavyW 12–⁠0–––––
Oct 13vs.Utah StateL 27–⁠49118––0
Dec 27 ✦vs.Bowling GreenW 29–⁠20223––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.