Preston North End star has just done what only TWO other players have - the last against Leeds United

Milutin Osmajic inspired Preston North End to victory over Huddersfield Town. (Image: CameraSport - Dave Howarth)Milutin Osmajic inspired Preston North End to victory over Huddersfield Town. (Image: CameraSport - Dave Howarth)
Milutin Osmajic inspired Preston North End to victory over Huddersfield Town. (Image: CameraSport - Dave Howarth) | CameraSport - Dave Howarth
History was made at Deepdale in Preston North End’s 4-1 win over Huddersfield Town.

Preston North End striker Milutin Osmajic scored a remarkable hat-trick in Tuesday's 4-1 win over Huddersfield Town.

After being introduced on 76 minutes, with the score 1-1 at Deepdale in a 'must win' game according to manager Ryan Lowe, Osmajic scored three goals in the space of seven minutes. He converted from Duane Holmes' cross, slotted home after Alan Browne's through ball and swept in from Mads Frokjaer's cross.  

Hide Ad
Hide Ad

And in doing so, Osmajic become only the third Preston player to score a hat-trick in the Championship for the Lilywhites. The last person to do that was Jon Parkin, in an incredible 6-4 win at Leeds United - whom PNE were 1-4 down against, back in September 2010. 

Prior to that, Richard Cresswell netted three first half goals at Deepdale, in an eventual 3-2 win over Sunderland. That clash took place in January 2005. The history books will need to be delved into, to work out whether Osmajic's hat-trick is the quickest by any PNE player ever. 

But, it is definitely the first, in the league, by a North End man since Joe Garner's, against Swindon Town in 2015. Jermaine Beckford, of course, went on to net three in the Play-Off final that campaign. And Simon Makienok grabbed the match ball, away to Bournemouth, in a 2016/17 cup tie. North End won that game 3-2, under Simon Grayson.

Comment Guidelines

National World encourages reader discussion on our stories. User feedback, insights and back-and-forth exchanges add a rich layer of context to reporting. Please review our Community Guidelines before commenting.