Running back, Pittsburgh, 2006–08
Kevin Collier
Lettered 2006 (school media guide)
- Number
- No. 24
- Height
- 5′11″
- Weight
- 210 lb
- Hometown
- Rochester, NY
Kevin Collier played running back at Pittsburgh (2006–08).
Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2006* | Pittsburgh | 33 | 115 | 3.5 | 2 | 16 |
| 2008* | Pittsburgh | 4 | 25 | 6.3 | 0 | 19 |
| Career | 37 | 140 | 3.8 | 2 | 19 | |
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.
On the roster
| Season | Team | No. | Pos | Ht | Wt |
|---|---|---|---|---|---|
| 2006 | Pittsburgh | 24 | RB | ||
| 2007 | Pittsburgh | 24 | RB | ||
| 2008 | Pittsburgh | 24 | RB | 5′11″ | 210 |
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
2008 Pittsburgh 2 games, 25 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 27 | at Syracuse | W 34–24 | 2 | 23 | 0 | 19 | – | – |
| Nov 8 | vs. Louisville | W 41–7 | 2 | 2 | 0 | 3 | – | – |
2006 Pittsburgh 7 games, 115 rushing yards, 2 TD
| Date | Opponent | Result | Car | Yds | TD | Long | Rec | Rec yds |
|---|---|---|---|---|---|---|---|---|
| Sep 2 | vs. Virginia | W 38–13 | 2 | 1 | 0 | 2 | – | – |
| Sep 8 | at Cincinnati | W 33–15 | 4 | 4 | 0 | 4 | – | – |
| Sep 23 | vs. The Citadel | W 51–6 | 13 | 54 | 1 | 16 | – | – |
| Sep 30 | vs. Toledo | W 45–3 | 5 | 19 | 1 | 10 | 1 | 7 |
| Oct 13 | at UCF | W 52–7 | 8 | 35 | 0 | 10 | – | – |
| Nov 16 | vs. West Virginia | L 27–45 | – | – | – | – | 1 | 8 |
| Nov 25 | vs.Louisville | L 24–48 | 1 | 2 | 0 | 2 | 1 | 3 |
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.