Indiana, 2005–06
Will Meyers
Will Meyers played at Indiana (2005–06).
Defense
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). ‡ Short by one game in 2005 (Oct 29 at Michigan State): the source has no box score for it. 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
| Season | G | Solo | Ast | Tkl | TFL | Sacks | Int | PBU | FF | Hur |
|---|---|---|---|---|---|---|---|---|---|---|
| 2005 | 11 | 63 | 20 | 83 | 7 | 1 | 1 | 3 | 1 | 1 |
| 2006 | 12 | 53 | 25 | 78 | 4 | 0 | 5 | 4 | 1 | 0 |
| On file | 116 | 45 | 161 | 11 | 1 | 6 | 7 | 2 | 1 | |
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.
Game by game
2006 Indiana 4 games with an interception on file, 5 INT
| Date | Opponent | Result | Int |
|---|---|---|---|
| Sep 2 | vs. Western Michigan | W 39–20 | 1 |
| Oct 14 | vs. Iowa | W 31–28 | 1 |
| Oct 28 | vs. Michigan State | W 46–21 | 1 |
| Nov 18 | at Purdue | L 19–28 | 2 |
2005 Indiana 1 game with an interception on file, 1 INT
| Date | Opponent | Result | Int |
|---|---|---|---|
| Oct 8 | vs. Illinois | W 36–13 | 1 |
No box score in the source for Oct 29 at Michigan State, so that game is not listed.
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.