Council refuses to disclose Alpamare financial losses before sale
Summarised from 2 outlets · Updated 18 Nov, 16:38 · Archive
Scarborough council will not reveal the cost to taxpayers of Alpamare waterpark until after selling it to a new owner.
Scarborough council is refusing to disclose how much taxpayers have lost on Alpamare waterpark until the sale to a preferred purchaser is completed. Tom Seston, a Reform councillor for Eastfield, asked at a full council meeting on 18 November when elected members and the public would be told the financial cost of what he called the 'Alpamare debacle'.
Cllr Peter Wilkinson, the council's executive member for finance and resources, said the information could not be released whilst the sale process was ongoing. He told councillors: 'The proposed disposal of the Alpamare site has not yet been completed, and as previously advised to members, this is commercially sensitive. However, the council will provide a transparent account of the financial position once this transaction has been completed.'
Operational management of Alpamare transferred from Flamingo Land to the council on 1 November. The authority said it will act as a caretaker for the site until it can be handed over to its new owner.
How it is being reported
- Answers demanded over 'Alpamare losses' ahead of saleQUESTIONS have been raised about how much taxpayers have lost on Scarborough's Alpamare waterpark amid continuing negotiations to sell the attraction to a new owner.The Press (York) · 18 Nov, 15:56
- Answers demanded over 'Alpamare losses' ahead of saleQUESTIONS have been raised about how much taxpayers have lost on Scarborough's Alpamare waterpark amid continuing negotiations to sell the attraction to a new owner.Gazette & Herald (Malton) · 18 Nov, 15:56
In this story: Scarborough council · Tom Seston · Alpamare · Flamingo Land · Peter Wilkinson
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)