Safety, Akron, 2008–⁠12

Josh Richmond

Number
No. 33
Height
5′11″
Hometown
Passaic, NJ

Josh Richmond played safety at Akron (2008–⁠12).

Defense

SeasonTeamInt
2010Akron1
2011*Akron1
2012*Akron1
Career3

Season lines from CollegeFootballData, regular season and bowls. * That team-season’s player lines are missing part of the team’s yards in our source, so these numbers may be short. 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

SeasonGSoloAstTklTFLSacksIntPBU
200966391000
2010103316491.50.513
201171611270.5010
20128126180010
On file673610330.533

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.PosHt
2009Akron33S
2010Akron33S
2011Akron33S
2012Akron33S5′11″

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 Akron 1 game with an interception on file, 1 INT
DateOpponentResultInt
Oct 6vs.Bowling GreenL 10–⁠241
2011 Akron 1 game with an interception on file, 1 INT
DateOpponentResultInt
Oct 22vs.OhioL 20–⁠371
2010 Akron 1 game with an interception on file, 1 INT
DateOpponentResultInt
Nov 26vs.BuffaloW 22–⁠141

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.