Delays to Grand Paris Express lines 15 and 18 raise cost and timeline concerns for Europe’s largest automated metro project
Executive summary: Le Monde reports that the first section of Grand Paris Express line 15 between Massy and Saclay, originally set to open on 1 October 2026, is delayed by at least two months, and the southern part of line 15 is now expected six months later than the planned spring 2027 launch. The delays increase the risk of cost overruns for the €35 billion automated metro, impact contracts with construction firms, and postpone expected economic benefits for the Île‑de‑France region.
Who is involved: Société du Grand Paris (project owner), construction consortia (including Eiffage, Vinci, and Bouygues), regional transport authority Île‑de‑France Mobilités, and the French government.
Likely next: Revised schedules will be submitted to regulators, potential penalty clauses may be triggered, and stakeholders will seek additional financing or cost‑saving measures.
The opening of the Massy‑Saclay segment of line 15 has been pushed back at least two months, while the southern section of line 15 now faces a six‑month slip to spring 2027. Line 18, initially slated for late 2026, also sees postponement. The setbacks add to a pattern of schedule slippages that have already inflated the project’s budget and may affect financing arrangements and regional development plans.
Timeline
- — Métro : de nouveaux retards pour les lignes 15 et 18 du Grand Paris Express (Le Monde — Économie)
- — Grand Paris Express : la ligne 15 Sud encore repoussée de plusieurs mois, la ligne 18 ouvrira début décembre (Le Figaro — Économie)
Analysis — what this means
Likely next events
- Updated opening dates to be announced by Société du Grand Paris later in Q3 2026
Sectors affected
- Construction
- Transport infrastructure
- Real estate development
- Public financing
Historical parallels
- Previous postponements of Grand Paris Express lines 14 and 16
- UK’s HS2 project faced similar multi‑year delays
- Berlin Brandenburg Airport experienced repeated schedule slips
Key entities
Sources
Open the full interactive case file on Beyond →