Receiver, Notre Dame, to 2005
Rashon Powers-Neal
Rashon Powers-Neal played receiver at Notre Dame (to 2005).
Career highs
3rushing touchdowns, best game on fileat Pittsburgh, 2005Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2004 | Notre Dame | 10 | 72 | 7.2 | 2 | 19 |
| 2005 | Notre Dame | 9 | 90 | 10.0 | 0 | 18 |
| On file (2004–05) | 19 | 162 | 8.5 | 2 | 19 | |
Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2004 | Notre Dame | 13 | 28 | 2.2 | 1 | 7 |
| 2005 | Notre Dame | 31 | 100 | 3.2 | 6 | 10 |
| On file (2004–05) | 44 | 128 | 2.9 | 7 | 10 | |
Season lines from CollegeFootballData, regular season and bowls. Every season here is summed from the game box scores (the source has no season lines for them; a game missing from the box scores is missing here).
Game by game
2005 Notre Dame 4 games, 100 rushing yards, 6 TD
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Sep 3 | at Pittsburgh | W 42–21 | 1 | 18 | 0 | 18 | 41 |
| Sep 10 | at Michigan | W 17–10 | 1 | 9 | 0 | 9 | 19 |
| Sep 24 | at Washington | W 36–17 | 4 | 28 | 0 | 11 | 30 |
| Oct 1 | at Purdue | W 49–28 | 3 | 35 | 0 | 15 | 10 |
2004 Notre Dame 10 games, 10 catches, 72 yards, 2 TD
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Sep 4 | at BYU | L 17–20 | 4 | 24 | 0 | 9 | 0 |
| Sep 11 | vs.Michigan | W 28–20 | 1 | 8 | 1 | 8 | – |
| Sep 18 | at Michigan State | W 31–24 | – | – | – | – | 0 |
| Sep 25 | vs.Washington | W 38–3 | – | – | – | – | 17 |
| Oct 2 | vs.Purdue | L 16–41 | 1 | 6 | 0 | 6 | 1 |
| Oct 9 | vs. Stanford | W 23–15 | 1 | 10 | 0 | 10 | 4 |
| Oct 23 | vs. Boston College | L 23–24 | – | – | – | – | 5 |
| Nov 6 | at Tennessee | W 17–13 | 1 | 3 | 0 | 3 | 1 |
| Nov 13 | vs.Pittsburgh | L 38–41 | 1 | 19 | 1 | 19 | – |
| Dec 28 ✦ | vs. Oregon State | L 21–38 | 1 | 2 | 0 | 2 | – |
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.