Fullback, Nebraska, 2009–11
Tyler Legate
- Number
- No. 48
- Height
- 5′10″
- Hometown
- Neligh, NE
Tyler Legate played fullback at Nebraska (2009–11).
Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2011 | Nebraska | 8 | 54 | 6.8 | 0 | 36 |
Receiving
Returns
Season lines from CollegeFootballData, regular season and bowls.
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
2011 Nebraska 8 games, 54 rushing yards
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Sep 3 | vs. Chattanooga | W 40–7 | 1 | 1 | 0 | – | – | – |
| Sep 17 | vs. Washington | W 51–38 | 2 | 37 | 0 | 1 | 3 | 1 |
| Sep 24 | at Wyoming | W 38–14 | 1 | 4 | 0 | 1 | 2 | 0 |
| Oct 1 | at Wisconsin | L 17–48 | 1 | 4 | 0 | – | – | – |
| Oct 22 | at Minnesota | W 41–14 | 1 | 3 | 0 | 1 | 10 | 1 |
| Oct 29 | vs. Michigan State | W 24–3 | 1 | 0 | 0 | – | – | – |
| Nov 25 | vs. Iowa | W 20–7 | 1 | 5 | 0 | – | – | – |
| Jan 2 ✦ | vs. South Carolina | L 13–30 | – | – | – | 1 | 6 | 0 |
2010 Nebraska 1 game, 1 catch, 1 yard, 1 TD
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Oct 23 | at Oklahoma State | W 51–41 | – | – | – | 1 | 1 | 1 |
2009 Nebraska 4 games, 3 catches, 27 yards, 1 TD
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Sep 12 | vs. Arkansas State | W 38–9 | – | – | – | 1 | 3 | 1 |
| Sep 26 | vs. Louisiana | W 55–0 | – | – | – | 1 | 11 | 0 |
| Oct 17 | vs. Texas Tech | L 10–31 | – | – | – | – | – | – |
| Nov 21 | vs. Kansas State | W 17–3 | – | – | – | 1 | 13 | 0 |
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.