Tight end, Ball State, 2009–11
Aaron Mershman
Lettered 2010–12 (school media guide)
- Number
- No. 11
- Height
- 6′2″
- Hometown
- Bowling Green, OH
Aaron Mershman played tight end at Ball State (2009–11).
Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2010 | Ball State | 13 | 125 | 9.6 | 1 | 25 |
| 2011 | Ball State | 5 | 28 | 5.6 | 1 | 14 |
| Career | 18 | 153 | 8.5 | 2 | 25 | |
Season lines from CollegeFootballData, regular season and bowls.
On the roster
| Season | Team | No. | Pos | Ht |
|---|---|---|---|---|
| 2009 | Ball State | 11 | TE | |
| 2010 | Ball State | 11 | TE | |
| 2011 | Ball State | 11 | TE | 6′2″ |
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 Ball State 3 games, 5 catches, 28 yards, 1 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 24 | vs. Army | W 48–21 | 2 | 17 | 0 | 14 |
| Oct 22 | vs. Central Michigan | W 31–27 | 3 | 11 | 1 | 6 |
| Oct 29 | at Western Michigan | L 35–45 | – | – | – | – |
No box score in the source for Nov 25 vs. Toledo, so that game is not listed.
2010 Ball State 9 games, 13 catches, 125 yards, 1 TD
| Date | Opponent | Result | Rec | Yds | TD | Long |
|---|---|---|---|---|---|---|
| Sep 2 | vs. Southeast Missouri State | W 27–10 | 1 | 8 | 0 | 8 |
| Sep 11 | vs. Liberty | L 23–27 | 2 | 40 | 1 | 25 |
| Sep 18 | at Purdue | L 13–24 | 1 | 9 | 0 | 9 |
| Sep 25 | at Iowa | L 0–45 | 2 | 19 | 0 | 14 |
| Oct 2 | atCentral Michigan | W 31–17 | 1 | 4 | 0 | 4 |
| Oct 9 | vs.Western Michigan | L 16–45 | 1 | 9 | 0 | 9 |
| Oct 16 | vs. Eastern Michigan | L 38–41 | 3 | 16 | 0 | 7 |
| Oct 23 | at Toledo | L 24–31 | 1 | 9 | 0 | 9 |
| Nov 6 | vs. Akron | W 37–30 | 1 | 11 | 0 | 11 |
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.