Running back, North Carolina, 2006–10
Anthony Elzy
- Number
- No. 6
- Height
- 5′10″
- Hometown
- Warren, OH
Anthony Elzy played running back at North Carolina (2006–10).
Career highs
116rushing yards, best game on fileat Duke, 20102rushing touchdowns, best game on filevs. James Madison, 20079catches, best game on filevs. NC State, 2010178receiving yards, best game on filevs. NC State, 2010Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2007* | North Carolina | 92 | 321 | 3.5 | 5 | 39 |
| 2008* | North Carolina | 3 | 5 | 1.7 | 0 | 4 |
| 2009 | North Carolina | 11 | 40 | 3.6 | 0 | 11 |
| 2010 | North Carolina | 72 | 296 | 4.1 | 2 | 25 |
| On file (2007–10) | 178 | 662 | 3.7 | 7 | 39 | |
Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2007* | North Carolina | 10 | 73 | 7.3 | 0 | 20 |
| 2008* | North Carolina | 7 | 86 | 12.3 | 0 | 19 |
| 2009 | North Carolina | 7 | 49 | 7.0 | 0 | 18 |
| 2010 | North Carolina | 25 | 338 | 13.5 | 2 | 52 |
| On file (2007–10) | 49 | 546 | 11.1 | 2 | 52 | |
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 | Ht |
|---|---|---|---|---|
| 2007 | North Carolina | 6 | RB | |
| 2008 | North Carolina | 6 | RB | |
| 2009 | North Carolina | 6 | RB | |
| 2010 | North Carolina | 6 | RB | 5′10″ |
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
2010 North Carolina 8 games, 296 rushing yards, 2 TD
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Sep 4 | vs. | L 24–30 | 14 | 46 | 0 | – | – | – |
| Sep 25 | at | W 17–13 | 1 | 7 | 0 | – | – | – |
| Oct 9 | vs. | W 21–16 | – | – | – | 1 | 3 | 0 |
| Oct 23 | at | L 10–33 | – | – | – | 1 | 9 | 0 |
| Nov 6 | at | W 37–35 | 5 | 13 | 0 | 3 | 25 | 1 |
| Nov 13 | vs. | L 10–26 | 17 | 82 | 1 | 7 | 102 | 0 |
| Nov 20 | vs. | L 25–29 | 12 | 32 | 0 | 9 | 178 | 1 |
| Nov 27 | at | W 24–19 | 23 | 116 | 1 | 4 | 21 | 0 |
2009 North Carolina 6 games, 40 rushing yards
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Sep 12 | at | W 12–10 | – | – | – | 2 | 25 | 0 |
| Sep 19 | vs. | W 31–17 | – | – | – | 3 | 11 | 0 |
| Oct 29 | at | W 20–17 | – | – | – | 1 | −1 | 0 |
| Nov 7 | vs. | W 19–6 | 2 | 12 | 0 | – | – | – |
| Nov 14 | vs. | W 33–24 | 1 | 3 | 0 | – | – | – |
| Nov 21 | at | W 31–13 | 8 | 25 | 0 | 1 | 14 | 0 |
2008 North Carolina 5 games, 5 rushing yards
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Sep 11 | at | W 44–12 | 1 | 0 | 0 | 1 | 19 | 0 |
| Sep 27 | at | W 28–24 | 2 | 5 | 0 | – | – | – |
| Oct 4 | vs. | W 38–12 | – | – | – | 3 | 38 | 0 |
| Oct 11 | vs. | W 29–24 | – | – | – | 1 | 4 | 0 |
| Oct 18 | at | L 13–16 | – | – | – | 2 | 25 | 0 |
2007 North Carolina 11 games, 321 rushing yards, 5 TD
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Sep 1 | vs. | W 37–14 | 11 | 28 | 2 | – | – | – |
| Sep 8 | at | L 31–34 | 8 | 23 | 0 | 1 | 6 | 0 |
| Sep 22 | at | L 10–37 | 2 | 3 | 0 | 1 | 4 | 0 |
| Sep 29 | at | L 10–17 | 11 | 74 | 1 | 2 | 25 | 0 |
| Oct 6 | vs. | W 33–27 | 25 | 95 | 1 | 4 | 39 | 0 |
| Oct 13 | vs. | L 15–21 | 11 | 23 | 0 | – | – | – |
| Oct 27 | at | L 10–37 | 5 | 18 | 0 | – | – | – |
| Nov 3 | vs. | W 16–13 | 8 | 37 | 0 | 1 | −6 | 0 |
| Nov 10 | at | L 27–31 | 4 | 10 | 0 | 1 | 5 | 0 |
| Nov 17 | at | L 25–27 | 6 | 10 | 1 | – | – | – |
| Nov 24 | vs. | W 20–14 | 1 | 0 | 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.
