British pubs set to earn $15m on Prince Harry's wedding day

Queen Elizabeth's grandson and Markle are set to tie the knot in a ceremony on May 19


Xinhua April 14, 2018
Queen Elizabeth's grandson and Markle are set to tie the knot in a ceremony on May 19. PHOTO: TELEGRAPH

LONDON: Pubs in Britain are expected to net a bonus of almost 15 million US dollars as people toast Prince Harry and American actress Meghan Markle on their wedding day, government minister Jake Berry announced Saturday.

Queen Elizabeth's grandson and Markle are to tie the knot in a ceremony on May 19 at Windsor Castle.

Berry said with just over 1 month to go until the big day, the drinks industry stands to get a multi-million dollar boost from the celebrations.

Meghan Markle's wedding hugely impacts 'Suits'

Pub opening hours have been extended for the special occasion and Berry is encouraging people to celebrate the big day with their community first at street parties, and later at their local pubs.

Across the country, local town and city councils are receiving hundreds of applications from residents wanting to hold street parties, said the Ministry of Housing, Communities and Local Government.

Meghan Markle dreamt of being a queen when she was just eight

Berry said: "Pubs are a cornerstone of many communities and I'm encouraging people to raise a glass to the happy couple in their local on May 19th. Up and down the country, councils have answered our call to make it easy for people to throw a street party fit for a prince and his bride."

Many councils, such as Salford near Manchester, are screening the royal wedding in local parks, while the London borough of Bromley has already received more than 60 street party applications, and Richmond in Surrey, more than 50.

COMMENTS (1)

BrainBro | 6 years ago | Reply Royal activity is good for UK businesses. Millions of people follow them; this is good for everyone involved money-wise.
Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ