Running back, Indiana State, 2022–24
Micah Hauser
- Number
- No. 29
- Height
- 5′11″
- Weight
- 185 lb
- Class (2024)
- Freshman
- Hometown
- Westfield, IN
Micah Hauser played running back at Indiana State (2022–24).
Defense
| Season | Team | Tkl | Solo | TFL | Sacks | PD | Hur |
|---|---|---|---|---|---|---|---|
| 2022 | Indiana State | 3 | 3 | 0 | 0 | 0 | 0 |
| 2023 | Indiana State | 6 | 3 | 0 | 0 | 0 | 0 |
| 2024* | Indiana State | 4 | 3 | 0 | 0 | 0 | 0 |
| Career | 13 | 9 | 0 | 0 | 0 | 0 | |
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 | Class | Ht | Wt |
|---|---|---|---|---|---|---|
| 2022 | Indiana State | 29 | RB | Yr 1 | ||
| 2023 | Indiana State | 29 | RB | Yr 2 | ||
| 2024 | Indiana State | 29 | RB | Fr. (Yr 3) | 5′11″ | 185 |
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
2024 Indiana State 1 game, 4 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Aug 31 | at Purdue | L 0–49 | 4 | 3 | 0 | 0 | 0 |
2023 Indiana State 2 games, 6 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 8 | at Indiana | L 7–41 | 5 | 3 | 0 | 0 | 0 |
| Sep 16 | at Ball State | L 7–45 | 1 | 0 | 0 | 0 | 0 |
2022 Indiana State 1 game, 3 tackles
| Date | Opponent | Result | Tkl | Solo | TFL | Sacks | PD |
|---|---|---|---|---|---|---|---|
| Sep 10 | atPurdue | L 0–56 | 3 | 3 | 0 | 0 | 0 |
No box score in the source for Oct 29 at South Dakota State, so that game is not listed.
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.