Railway arches in Carlisle to reopen after £1.6m investment
Summarised from 2 outlets · Updated 5 Nov, 13:55 · Archive
The Arch Company is investing £1.6m to restore 12 railway arches in Carlisle that have been empty since flooding in 2015.
The Arch Company bought 12 railway arches in Carlisle from Network Rail in 2019 with plans to restore them into modern commercial spaces. The units on Viaduct Estate Road have been empty since Storm Desmond caused major flooding in 2015, leaving the area quieter and affecting local businesses.
The £1.6m refurbishment will upgrade the arches with new glazing, roller shutters, improved power supplies, lighting, signage, toilet facilities and restored forecourts. They were previously used as retail units and will offer flexible business space to attract new enterprises to the city centre.
Improved flood defences along the River Caldew have made the investment possible. James Seabrooke, the Arch Company's development director, said the upgraded defences were the 'key factor' giving them confidence to invest. Jo Secular-Hall, who owns a carpet and interiors shop opposite the site, welcomed the scheme, saying the area had lost footfall since the floods and that reopening the arches 'can only be a good thing'.
The units have not yet been marketed but are expected to be ready to lease in 2027.

How it is being reported
- Hopes for flood-hit rail arches in £1.6m revampThe arches in Carlisle city centre, which closed in 2015, are expected to be ready in the new year.BBC Cumbria · 5 Nov, 13:22
- £1.6m investment to transform 12 'long-empty' railway arches in cityThe Arch Company is investing £1.6m to transform 12 long-empty railway arches in Carlisle into modern commercial spaces, boosting the city centre economy.News & Star · 3 Nov, 16:09
In this story: The Arch Company · Carlisle · Network Rail · Viaduct Estate Road · West Coast Main Line
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)