Receiver, North Carolina, 2003–05
Mike Mason
Mike Mason played receiver at North Carolina (2003–05).
Career highs
82receiving yards, best game on filevs. Utah, 2005Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2004 | North Carolina | 19 | 272 | 14.3 | 1 | 35 |
| 2005 | North Carolina | 22 | 372 | 16.9 | 1 | 44 |
| On file (2004–05) | 41 | 644 | 15.7 | 2 | 44 | |
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 North Carolina 9 games, 22 catches, 372 yards, 1 TD
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Sep 10 | at Georgia Tech | L 21–27 | 2 | 35 | 0 | 28 | – |
| Sep 24 | at NC State | W 31–24 | 3 | 61 | 0 | 32 | −7 |
| Oct 1 | vs. Utah | W 31–17 | 4 | 82 | 0 | 40 | – |
| Oct 8 | at Louisville | L 14–69 | 3 | 66 | 0 | 27 | – |
| Oct 29 | at Miami | L 16–34 | 1 | 5 | 0 | 5 | – |
| Nov 5 | vs. Boston College | W 16–14 | 2 | 3 | 0 | 3 | – |
| Nov 12 | vs. Maryland | L 30–33 | 3 | 72 | 1 | 44 | – |
| Nov 19 | vs. Duke | W 24–21 | 2 | 32 | 0 | 19 | – |
| Nov 26 | at Virginia Tech | L 3–30 | 2 | 16 | 0 | 11 | – |
2004 North Carolina 9 games, 19 catches, 272 yards, 1 TD
| Date | Opponent | Result | Rec | Yds | TD | Long | Rush |
|---|---|---|---|---|---|---|---|
| Sep 11 | at Virginia | L 24–56 | 1 | 2 | 0 | 2 | – |
| Sep 25 | vs.Louisville | L 0–34 | 2 | 49 | 0 | 34 | – |
| Oct 2 | at Florida State | L 16–38 | 2 | 19 | 0 | 14 | 0 |
| Oct 9 | vs.NC State | W 30–24 | 1 | 7 | 0 | 7 | – |
| Oct 16 | atUtah | L 16–46 | 3 | 46 | 0 | 35 | – |
| Oct 30 | vs.Miami | W 31–28 | 2 | 42 | 1 | 35 | – |
| Nov 6 | vs.Virginia Tech | L 24–27 | 2 | 42 | 0 | 30 | – |
| Nov 13 | at Wake Forest | W 31–24 | 2 | 8 | 0 | 8 | – |
| Nov 20 | atDuke | W 40–17 | 4 | 57 | 0 | 20 | – |
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.