Fullback, Stanford, 2008–09
Josh Catron
- Number
- No. 47
- Height
- 6′0″
- Hometown
- Torrance, CA
Josh Catron played fullback at Stanford (2008–09).
Returns
| Season | Team | KR | Yds | TD |
|---|---|---|---|---|
| 2009 | Stanford | 8 | 77 | 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.
Defense before 2016
| Season | G | Solo | Ast | Tkl |
|---|---|---|---|---|
| 2006N | 8 | 2 | 0 | 2 |
| 2007N | 9 | 3 | 1 | 4 |
| 2008 | 7 | 5 | 0 | 5 |
| 2009 | 9 | 6 | 8 | 14 |
| On file | 16 | 9 | 25 | |
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
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
2009 Stanford 7 games, 8 returns, 77 yards
| Date | Opponent | Result | KR | Yds | TD |
|---|---|---|---|---|---|
| Sep 12 | at | L 17–24 | 3 | 11 | 0 |
| Sep 19 | vs. | W 42–17 | 1 | 10 | 0 |
| Sep 26 | vs. | W 34–14 | 1 | 14 | 0 |
| Nov 7 | vs. | W 51–42 | – | – | – |
| Nov 14 | at | W 55–21 | – | – | – |
| Nov 21 | vs. | L 28–34 | 1 | 14 | 0 |
| Nov 28 | vs. | W 45–38 | 2 | 28 | 0 |
2008 Stanford 4 games, 4 rushing yards
| Date | Opponent | Result | KR | Yds | TD |
|---|---|---|---|---|---|
| Oct 11 | vs. | W 24–23 | – | – | – |
| Nov 1 | vs. | W 58–0 | – | – | – |
| Nov 8 | at | L 28–35 | – | – | – |
| Nov 22 | at | L 16–37 | – | – | – |
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.
