Stay up to date with notifications from The Independent

Notifications can be managed in browser preferences.

Burnley vs Watford clash given third date after being postponed twice

The fixture was postponed for a second time earlier this week.

Ian Parker
Friday 21 January 2022 10:29 GMT
Comments
Burnley’s Premier League match against Watford has been rearranged for February 5 (Zac Goodwin/PA)
Burnley’s Premier League match against Watford has been rearranged for February 5 (Zac Goodwin/PA) (PA Wire)

Burnley and Watford will hope it is third time lucky as their Premier League fixture has been rearranged for February 5 with a 6pm kick-off time.

The fixture was postponed for a second time earlier this week. It was originally due to be played on December 15 but was called off due to Covid-19 cases within the Watford squad before an outbreak at Burnley forced the postponement of the rearranged match on January 18.

But with both sides having already been knocked out of the FA Cup, it has been rescheduled for the weekend of the fourth-round fixtures.

On Thursday, Watford boss Claudio Ranieri had urged the Premier League to make an exception and allow the match to go ahead next weekend, which has been left blank for a winter break that coincides with World Cup qualifiers in North and South America.

“I hope when we play against Burnley we will have some more days to recover for another match,” Ranieri said. “We have a week free and we can maybe play a little earlier.”

The match is one of five that Burnley, bottom of the table having played the fewest matches of any top-flight side this season, needed to rearrange.

They have also seen matches against Everton Aston Villa and Leicester postponed due to Covid-19, while November’s fixture against Tottenham was called off due to heavy snow.

Join our commenting forum

Join thought-provoking conversations, follow other Independent readers and see their replies

Comments

Thank you for registering

Please refresh the page or navigate to another page on the site to be automatically logged inPlease refresh your browser to be logged in