Running back, Lamar, 2016
Austin Krautz
- Hometown
- Nederland, TX
Austin Krautz played running back at Lamar (2016).
Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2016 | Lamar | 1 | 2 | 2.0 | 0 | 2 |
Season lines from CollegeFootballData, regular season and bowls.
Per play
| Season | Team | Plays | EPA/play | Pctile | Median | Total | Usage |
|---|---|---|---|---|---|---|---|
| 2016 | Lamar (FCS) | 1 | -0.36 | – | – | -0.4 | – |
Expected points added: how much the player’s plays moved the team’s expected score, per play and in total. Plays: total EPA divided by EPA per play, the plays the source credits to him (for a receiver roughly his catches and runs, not every target; for a passer, not every attempt), so it can differ from attempts plus carries. Percentile: against the position’s regulars that season across all divisions on file (quarterbacks with 150+ plays, backs 60+, receivers and tight ends 30+), with how many there were (n) and their median; a dash means too few plays to rank. A season in progress uses the full-season bar scaled by games played, never below 75 plays for quarterbacks, 30 for backs and 20 for receivers. The cohort grows or shrinks with the source’s coverage each season (2025 lists far more players), so compare percentiles rather than raw EPA across years. FCS seasons are marked. Usage: the share of the team’s plays the player was part of (shown from 20 plays). From CollegeFootballData, 2013 on.
Game by game
2016 Lamar 1 game, 2 rushing yards
| Date | Opponent | Result | Car | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 10 | at | L 0–42 | 1 | 2 | 0 | 2 |
No box score in the source for Sep 4 vs. Coastal Carolina; Sep 18 vs. Sam Houston; Oct 2 vs. SE Louisiana; Oct 8 at Abilene Christian; Oct 15 vs. Northwestern State; Oct 22 at Central Arkansas; Oct 29 vs. Houston Christian; Nov 3 at Nicholls; Nov 13 vs. Incarnate Word; Nov 20 at McNeese, so those games are 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.
