Punter, Notre Dame (from Wake Forest), 2009–⁠13

Alex Wulfeck

Number
No. 98
Height
5′9″
Hometown
Orange Park, FL

Alex Wulfeck played punter at Wake Forest (2009–⁠11) and Notre Dame (2013).

Punting

Punting yards, season by season, with his team’s record
SeasonTeamPuntsYdsAvgLongIn 20
2010Wake Forest26834.0360
2011Wake Forest702,78039.7590
2013*Notre Dame826132.6490
Career803,10938.9590

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

SeasonTeamNo.PosHt
2009Wake Forest98P
2010Wake Forest98P
2011Wake Forest98P
2013Notre Dame98P5′9″

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

2013 Notre Dame 6 games, 8 punts, 32.6 average
DateOpponentResultPuntsYdsLongIn 20
Sep 14atPurdueW 31–⁠24138380
Sep 21vs.Michigan StateW 17–⁠13149490
Sep 28vs.OklahomaL 21–⁠35137370
Oct 5vs.Arizona StateW 37–⁠34380270
Oct 19vs.USCW 14–⁠10132320
Dec 28 ✦vs.RutgersW 29–⁠16125250
2011 Wake Forest 13 games, 70 punts, 39.7 average
DateOpponentResultPuntsYdsLongIn 20
Sep 1atSyracuseL 29–⁠364138380
Sep 10vs.NC StateW 34–⁠275184440
Sep 17vs.Gardner-WebbW 48–⁠5270370
Oct 1atBoston CollegeW 27–⁠195189440
Oct 8vs.Florida StateW 35–⁠307260450
Oct 15vs.Virginia TechL 17–⁠387301490
Oct 22atDukeW 24–⁠237267450
Oct 29atNorth CarolinaL 24–⁠493147590
Nov 5vs.Notre DameL 17–⁠245187440
Nov 12atClemsonL 28–⁠315219550
Nov 19vs.MarylandW 31–⁠105195450
Nov 26vs.VanderbiltL 7–⁠417303540
Dec 30 ✦vs.Mississippi StateL 17–⁠238320490
2010 Wake Forest 1 game, 2 punts, 34.0 average
DateOpponentResultPuntsYdsLongIn 20
Oct 30atMarylandL 14–⁠62268360

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.