Fullback, Wake Forest, 2005–09
Mike Rinfrette
- Number
- No. 44
- Height
- 6′3″
- Hometown
- Bunn, NC
Mike Rinfrette played fullback at Wake Forest (2005–09).
Team titles: ACC champions, 2006
Rushing
| Season | Team | Car | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2006* | Wake Forest | 6 | 18 | 3.0 | 1 | 6 |
| 2008* | Wake Forest | 25 | 64 | 2.6 | 1 | 7 |
| 2009 | Wake Forest | 26 | 54 | 2.1 | 3 | 6 |
| On file (2006–09) | 57 | 136 | 2.4 | 5 | 7 | |
Receiving
| Season | Team | Rec | Yds | Avg | TD | Long |
|---|---|---|---|---|---|---|
| 2006* | Wake Forest | 2 | 22 | 11.0 | 0 | 18 |
| 2008* | Wake Forest | 8 | 73 | 9.1 | 1 | 20 |
| 2009 | Wake Forest | 19 | 207 | 10.9 | 0 | 37 |
| On file (2006–09) | 29 | 302 | 10.4 | 1 | 37 | |
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.
Defense before 2016
| Season | G | Solo | Ast | Tkl | TFL | PBU |
|---|---|---|---|---|---|---|
| 2007 | 10 | 13 | 10 | 23 | 2 | 2 |
Our box scores carry tackles, tackles for loss and sacks from 2016 only, so these come from other sources: cfbstats.com (Open Data Commons Attribution License), its game lines summed (G: the games he has a line in). A dash: the source has no number for it.
On the roster
| Season | Team | No. | Pos | Ht |
|---|---|---|---|---|
| 2006 | Wake Forest | 44 | FB | |
| 2007 | Wake Forest | 44 | FB | |
| 2008 | Wake Forest | 44 | FB | |
| 2009 | Wake Forest | 44 | FB | 6′3″ |
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
2009 Wake Forest 12 games, 54 rushing yards, 3 TD
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Sep 5 | vs. Baylor | L 21–24 | 3 | 10 | 1 | – | – | – |
| Sep 12 | vs. Stanford | W 24–17 | 4 | 10 | 1 | 1 | 8 | 0 |
| Sep 19 | vs. Elon | W 35–7 | 3 | 11 | 1 | – | – | – |
| Sep 26 | at Boston College | L 24–27 | 2 | 2 | 0 | 1 | 8 | 0 |
| Oct 3 | vs. NC State | W 30–24 | 3 | 2 | 0 | 3 | 22 | 0 |
| Oct 10 | vs. Maryland | W 42–32 | 3 | 9 | 0 | 3 | 26 | 0 |
| Oct 17 | at Clemson | L 3–38 | 5 | 8 | 0 | 1 | 4 | 0 |
| Oct 24 | at Navy | L 10–13 | 3 | 2 | 0 | – | – | – |
| Oct 31 | vs. Miami | L 27–28 | – | – | – | 4 | 44 | 0 |
| Nov 7 | at Georgia Tech | L 27–30 | – | – | – | 2 | 27 | 0 |
| Nov 14 | vs. Florida State | L 28–41 | – | – | – | 3 | 31 | 0 |
| Nov 28 | at Duke | W 45–34 | – | – | – | 1 | 37 | 0 |
2008 Wake Forest 9 games, 64 rushing yards, 1 TD
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Sep 6 | vs. Ole Miss | W 30–28 | 2 | 7 | 0 | 1 | 6 | 0 |
| Sep 20 | atFlorida State | W 12–3 | – | – | – | 1 | 12 | 0 |
| Sep 27 | vs.Navy | L 17–24 | 1 | 0 | 0 | 1 | 8 | 1 |
| Oct 18 | atMaryland | L 0–26 | – | – | – | 1 | 20 | 0 |
| Oct 25 | atMiami | L 10–16 | 9 | 30 | 1 | – | – | – |
| Nov 1 | vs.Duke | W 33–30 | 3 | 5 | 0 | 3 | 22 | 0 |
| Nov 8 | vs. Virginia | W 28–17 | 6 | 10 | 0 | 1 | 5 | 0 |
| Nov 15 | atNC State | L 17–21 | 1 | 0 | 0 | – | – | – |
| Dec 20 ✦ | vs.Navy | W 29–19 | 3 | 12 | 0 | – | – | – |
2006 Wake Forest 7 games, 18 rushing yards, 1 TD
| Date | Opponent | Result | Car | Rush yds | Rush TD | Rec | Rec yds | Rec TD |
|---|---|---|---|---|---|---|---|---|
| Sep 23 | atOle Miss | W 27–3 | 2 | 4 | 1 | – | – | – |
| Sep 30 | vs. Liberty | W 34–14 | 1 | 6 | 0 | – | – | – |
| Oct 7 | vs.Clemson | L 17–27 | – | – | – | 1 | 4 | 0 |
| Oct 28 | at North Carolina | W 24–17 | 1 | 4 | 0 | – | – | – |
| Nov 4 | vs.Boston College | W 21–14 | 1 | 5 | 0 | – | – | – |
| Nov 11 | atFlorida State | W 30–0 | 1 | −1 | 0 | – | – | – |
| Dec 2 | vs.Georgia Tech | W 9–6 | – | – | – | 1 | 18 | 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.