Safety, Kent State, 2006–⁠10

Dan Hartman

Number
No. 38
Height
6′2″
Hometown
Leavittsburg, OH

Dan Hartman played safety at Kent State (2006–⁠10).

Defense

SeasonTeamInt
2009Kent State4
2010Kent State2
On file (2009–⁠10)6

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

SeasonGSoloAstTklTFLIntPBUFF
2007N111718350.5–1–
2008N112121421.5–1–
2009124824726491
2010113524592232
On file1218720810–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
2009Kent State38S
2010Kent State38S6′2″

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

2010 Kent State 1 game with an interception on file, 2 INT
DateOpponentResultInt
Nov 26vs.OhioW 28–⁠62
2009 Kent State 4 games with an interception on file, 4 INT
DateOpponentResultInt
Sep 26vs.Miami (OH)W 29–⁠191
Oct 17atEastern MichiganW 28–⁠61
Oct 24atOhioW 20–⁠111
Nov 27vs.BuffaloL 6–⁠91

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.