In planning

Data4 PAR03 — Nozay

Nozay, Essonne, France

Reviewed 27 Sept 20266 sources

Watch this site

Watch Data4 PAR03 — Nozay

Register interest in updates to planning status, grid position, capacity claims, delivery teams and policy exposure. Every Power Reality Check client receives 60 days of Site Watch on their assessed site when monitoring is available.

Project brief

Nozay redevelopment with three proposed data-centre buildings, a substation and heat recovery. The whole acquired holding and the application footprint differ.

Read overview

Current evidenceIn planning

6 cited sources · 8 utility and planning categories reviewed.

Review evidence and gaps

Next check

Obtain the connection agreement and updated reinforcement/energisation milestones.

Open the full check

Overview

Nozay redevelopment with three proposed data-centre buildings, a substation and heat recovery. The whole acquired holding and the application footprint differ.

Developer / applicant: Data4
Owner: DATA4 NOZAY SAS (acquisition stated in the inquiry; title unverified)
Operator: Data4

Planning and delivery status

February 2026 inquiry opinions support the applications with a grid-procedure reservation. Final permissions and data-hall construction commencement remain unverified.

Stage source: 15 Feb 2026

Project intelligence. This record does not establish that the land or facility is available to acquire.

POWER STUDY

Power

What the power evidence establishes

The site-specific connection scope has not been established for this record.

Power classDNo qualifying rung

No same-scope, dated import-MVA rung has document-seen or better verification. Nearby infrastructure, IT MW and marketing claims cannot upgrade the class.

The class describes published documentary evidence at its stated date. It does not prove current contractual rights, transferability or an energisation date.

Class describes evidence maturity. Public records do not prove current contractual rights, transferable capacity or an energisation date. This record has not received a complete power study review.

Read the rules and verification levels

Capacity ladder and evidence

Each rung is a separate MVA claim for its stated site or phase. A missing rung is unknown.

Applied

Unknown

Not established from the public records reviewed.

What applied mva is evidenced for the assessed site scope?

Event date

Unknown

Not established from the public records reviewed.

What is the effective date of the applied connection evidence?

Capacity boundary

Unknown

Not established from the public records reviewed.

Which buildings or phases does the applied connection evidence cover?

Verification

Unknown

Offered

Unknown

Not established from the public records reviewed.

What offered mva is evidenced for the assessed site scope?

Event date

Unknown

Not established from the public records reviewed.

What is the effective date of the offered connection evidence?

Capacity boundary

Unknown

Not established from the public records reviewed.

Which buildings or phases does the offered connection evidence cover?

Verification

Unknown

Accepted / contracted

Unknown

Not established from the public records reviewed.

What accepted or contracted mva is evidenced for the assessed site scope?

Event date

Unknown

Not established from the public records reviewed.

What is the effective date of the accepted connection evidence?

Capacity boundary

Unknown

Not established from the public records reviewed.

Which buildings or phases does the accepted connection evidence cover?

Verification

Unknown

Energised

Unknown

Not established from the public records reviewed.

What energised mva is evidenced for the assessed site scope?

Event date

Unknown

Not established from the public records reviewed.

What is the effective date of the energised connection evidence?

Capacity boundary

Unknown

Not established from the public records reviewed.

Which buildings or phases does the energised connection evidence cover?

Verification

Unknown

Connection point and load boundaries

Network operator: Unknown
Not established from the public records reviewed.
Which TSO or DSO is responsible for this demand connection?
Connection point: Unknown
Not established from the public records reviewed.
What is the operator-confirmed connection substation or circuit?
Voltage: Unknown
Not established from the public records reviewed.
What voltage level is specified for the demand connection?
Straight-line distance: Unknown
Not established from the public records reviewed.
What are the evidenced site and connection-point coordinates, and their calculated straight-line distance?
Published route length: Unknown
Not established from the public records reviewed.
What grid route length is published, and for which circuit?

IT load

Unknown

Not established from the public records reviewed.

What is the published IT load in MW?

Basis

Unknown

Not established from the public records reviewed.

On what electrical basis is the IT load in MW stated?

Site / phase boundary

Unknown

Not established from the public records reviewed.

Which phase or campus does the IT load in MW cover?

Facility load

Unknown

Not established from the public records reviewed.

What is the published facility load in MW?

Basis

Unknown

Not established from the public records reviewed.

On what electrical basis is the facility load in MW stated?

Site / phase boundary

Unknown

Not established from the public records reviewed.

Which phase or campus does the facility load in MW cover?

Import capacity

Unknown

Not established from the public records reviewed.

What is the published import capacity in MVA?

Basis

Unknown

Not established from the public records reviewed.

On what electrical basis is the import capacity in MVA stated?

Site / phase boundary

Unknown

Not established from the public records reviewed.

Which phase or campus does the import capacity in MVA cover?

These are different electrical quantities. No power factor, PUE or available import is assumed from an IT-load statement.

Connection agreement and conditions

Agreement type: Unknown
Not established from the public records reviewed.
What connection agreement type and current status are documented?
Phased capacity: Unknown
Not established from the public records reviewed.
Does the agreement impose phased import-capacity limits?
Flexibility obligations: Unknown
Not established from the public records reviewed.
What flexibility or curtailment obligations apply?
On-site generation obligations: Unknown
Not established from the public records reviewed.
What on-site generation obligations apply?
Securities posted: Unknown
Not established from the public records reviewed.
What securities are required, posted and still valid?
Longstop dates: Unknown
Not established from the public records reviewed.
What connection longstop or milestone dates apply?

Conflicts and scope comparisons

No conflicting pair is recorded. This does not establish that all public statements have been reconciled.

France grid context

Network publications frame the claim. They do not allocate capacity to this site.

No country context entries have been linked to this site. Applicable policy, capacity information and reinforcement dependencies need review.

Derived energisation window

Earliest plausible yearUnknown

Latest plausible yearUnknown

The observed inputs do not establish a bounded delivery range. Open bounds stay unknown.

Rule

Use only a same-scope, dated, document-verified capacity rung and an applicable duration to energisation published by the observed site operator. The named process operator and a named source publisher must match that operator. Earliest year is the maximum of stage date plus minimum duration and each evidenced readiness constraint. Latest year is the maximum of stage date plus maximum duration and each published upper constraint only when every required input is bounded. An offer-processing duration is excluded. A missing required input leaves the affected bound unknown; no padding or contractual delivery promise is inferred.

No observed inputs establish this result.

Dependencies driving the range

Connection-dependent reinforcement scope and completion dates: unknown.
Grid-works planning status and programme: unknown.
Applicable connection-policy conditions and programme: unknown.

What the earliest case requires

Connection-dependent reinforcement scope and completion dates introduces no later constraint than the earliest case; this remains unverified.
Grid-works planning status and programme introduces no later constraint than the earliest case; this remains unverified.
Applicable connection-policy conditions and programme introduces no later constraint than the earliest case; this remains unverified.

Missing inputs leave the range open

A dated, document-verified import-MVA rung for the assessed scope.
An applicable duration from the evidenced stage to energisation, published by and matched to the observed site operator, rather than an offer-processing target.
Connection-dependent reinforcement scope and completion dates
Grid-works planning status and programme
Applicable connection-policy conditions and programme

Indicative HV and connection capex

Unknown

Rule and scope

Sum each published complete scope quantity multiplied by the matching published benchmark minimum and maximum. Configuration, voltage, route type, unit, country applicability, currency and explicit price base year must match. No assumed route length, transformer count, exchange rate, inflation, fee uplift or partial index is inserted. The result is an indicative benchmark band, not an operator quotation or contractual connection charge.

No observed inputs establish this result.

Published connection works scope

Unknown

Not established from the public records reviewed.

What complete connection scope is published: bays, stations, voltage, circuits, route lengths and underground or overhead configuration?

Scope completeness

Unknown

Not established from the public records reviewed.

Is the published connection scope complete enough to match every component to a sourced benchmark?

Scope questions

Obtain a published complete connection scope with voltage, configuration and measured quantities.
Establish that every necessary connection-work component is included in the published scope.
Identify network and customer works, upstream reinforcement, land and wayleaves, taxes, fees, securities, contingency and the price base.

Alternatives and policy exposure

Behind-the-meter generation

Unknown

Not established from the public records reviewed.

What behind-the-meter generation is evidenced, and at what scope?

Planning / policy requirement

Unknown

Not established from the public records reviewed.

Does the applicable planning or connection policy require behind-the-meter generation?

Battery storage

Unknown

Not established from the public records reviewed.

What battery storage is evidenced, and at what scope?

Planning / policy requirement

Unknown

Not established from the public records reviewed.

Does the applicable planning or connection policy require battery storage?

Private wire

Unknown

Not established from the public records reviewed.

What a private wire is evidenced, and at what scope?

Planning / policy requirement

Unknown

Not established from the public records reviewed.

Does the applicable planning or connection policy require a private wire?

Gas

Unknown

Not established from the public records reviewed.

What gas supply or generation is evidenced, and at what scope?

Planning / policy requirement

Unknown

Not established from the public records reviewed.

Does the applicable planning or connection policy require gas supply or generation?

Connection claim against current policy

Unknown

Not established from the public records reviewed.

Does the published connection claim meet the policy applicable to its application date, location and agreement status?

Open questions for a Reality Check

Generated from unknown fields, missing derivation inputs and unresolved evidence. The questions identify the documents or specialist checks needed next.

60 questions to resolve

Which TSO or DSO is responsible for this demand connection?
Not established from the public records reviewed.
What is the operator-confirmed connection substation or circuit?
Not established from the public records reviewed.
What voltage level is specified for the demand connection?
Not established from the public records reviewed.
What are the evidenced site and connection-point coordinates, and their calculated straight-line distance?
Not established from the public records reviewed.
What grid route length is published, and for which circuit?
Not established from the public records reviewed.
What applied mva is evidenced for the assessed site scope?
Not established from the public records reviewed.
What is the effective date of the applied connection evidence?
Not established from the public records reviewed.
Which buildings or phases does the applied connection evidence cover?
Not established from the public records reviewed.
What evidence level can be supported for capacityLadder.applied?
Verification has not been established.
What offered mva is evidenced for the assessed site scope?
Not established from the public records reviewed.
What is the effective date of the offered connection evidence?
Not established from the public records reviewed.
Which buildings or phases does the offered connection evidence cover?
Not established from the public records reviewed.
What evidence level can be supported for capacityLadder.offered?
Verification has not been established.
What accepted or contracted mva is evidenced for the assessed site scope?
Not established from the public records reviewed.
What is the effective date of the accepted connection evidence?
Not established from the public records reviewed.
Which buildings or phases does the accepted connection evidence cover?
Not established from the public records reviewed.
What evidence level can be supported for capacityLadder.accepted?
Verification has not been established.
What energised mva is evidenced for the assessed site scope?
Not established from the public records reviewed.
What is the effective date of the energised connection evidence?
Not established from the public records reviewed.
Which buildings or phases does the energised connection evidence cover?
Not established from the public records reviewed.
What evidence level can be supported for capacityLadder.energised?
Verification has not been established.
What connection agreement type and current status are documented?
Not established from the public records reviewed.
Does the agreement impose phased import-capacity limits?
Not established from the public records reviewed.
What flexibility or curtailment obligations apply?
Not established from the public records reviewed.
What on-site generation obligations apply?
Not established from the public records reviewed.
What securities are required, posted and still valid?
Not established from the public records reviewed.
What connection longstop or milestone dates apply?
Not established from the public records reviewed.
What is the published IT load in MW?
Not established from the public records reviewed.
On what electrical basis is the IT load in MW stated?
Not established from the public records reviewed.
Which phase or campus does the IT load in MW cover?
Not established from the public records reviewed.
What is the published facility load in MW?
Not established from the public records reviewed.
On what electrical basis is the facility load in MW stated?
Not established from the public records reviewed.
Which phase or campus does the facility load in MW cover?
Not established from the public records reviewed.
What is the published import capacity in MVA?
Not established from the public records reviewed.
On what electrical basis is the import capacity in MVA stated?
Not established from the public records reviewed.
Which phase or campus does the import capacity in MVA cover?
Not established from the public records reviewed.
What operator-published connection-to-energisation duration applies to this site and connection stage?
An application-to-offer processing target is not an energisation duration.
Which reinforcements does the connection depend on, and what dates are published?
Not established from the public records reviewed.
Which grid works require planning, and what is their current consent status and dated programme?
Not established from the public records reviewed.
Which connection-policy conditions apply, and when could they be satisfied?
Not established from the public records reviewed.
What complete connection scope is published: bays, stations, voltage, circuits, route lengths and underground or overhead configuration?
Not established from the public records reviewed.
Is the published connection scope complete enough to match every component to a sourced benchmark?
Not established from the public records reviewed.
What behind-the-meter generation is evidenced, and at what scope?
Not established from the public records reviewed.
Does the applicable planning or connection policy require behind-the-meter generation?
Not established from the public records reviewed.
What battery storage is evidenced, and at what scope?
Not established from the public records reviewed.
Does the applicable planning or connection policy require battery storage?
Not established from the public records reviewed.
What a private wire is evidenced, and at what scope?
Not established from the public records reviewed.
Does the applicable planning or connection policy require a private wire?
Not established from the public records reviewed.
What gas supply or generation is evidenced, and at what scope?
Not established from the public records reviewed.
Does the applicable planning or connection policy require gas supply or generation?
Not established from the public records reviewed.
Does the published connection claim meet the policy applicable to its application date, location and agreement status?
Not established from the public records reviewed.
Which checked country-grid sources and location-specific constraints apply to this connection?
No country-context relationship has been established for this record.
Identify network and customer works, upstream reinforcement, land and wayleaves, taxes, fees, securities, contingency and the price base.
Connection-cost scope question.
Resolve the energisation input: A dated, document-verified import-MVA rung for the assessed scope.
This missing input leaves an energisation bound unknown.
Resolve the energisation input: An applicable duration from the evidenced stage to energisation, published by and matched to the observed site operator, rather than an offer-processing target.
This missing input leaves an energisation bound unknown.
Resolve the energisation input: Connection-dependent reinforcement scope and completion dates
This missing input leaves an energisation bound unknown.
Resolve the energisation input: Grid-works planning status and programme
This missing input leaves an energisation bound unknown.
Resolve the energisation input: Applicable connection-policy conditions and programme
This missing input leaves an energisation bound unknown.
Obtain a published complete connection scope with voltage, configuration and measured quantities.
This scope or reference gap prevents a complete indicative connection capex band.
Establish that every necessary connection-work component is included in the published scope.
This scope or reference gap prevents a complete indicative connection capex band.

Use these questions to scope a Power Reality Check.

Request an assessment of this record and the evidence needed next. Share only public information or documents you are authorised to provide.

Request a Reality Check

Earlier capacity notes and source context

250 MW importProject capacity

Proposed grid-connection demand in the MRAe opinion; not secured import or IT load. The opinion identifies excess connection capacity beyond this project’s needs.

Published claimProject source record

75 MW ITDC01 planned IT

Planned building IT load; not live or secured import.

Published claimCapacity source

37.5 MW ITDC02 planned IT

Planned building IT load; not live or secured import.

Published claimCapacity source

15 MW ITDC03 planned IT

Planned building IT load; not live or secured import.

Published claimCapacity source

Import rights and connection evidence

MRAe describes a proposed double 225 kV underground link of about 3.6 km from Escargot and reinforcement at Les Loges. The 250 MW connection request is distinct from IT load.

IT load, facility demand, import capacity and equipment ratings retain their stated scope. A published figure does not establish spare or transferable supply.

Planning & utilities

8 of 10 categories contain evidence. Each status applies to its specific claim.

Planning & decisions

Partial evidence

The inquiry supports environment and three building applications; grid DUP support carries a consultation reservation. Final decisions remain unverified.

Sources & next check

Evidence reviewed 27 Sept 2026

Next check

Retrieve signed grants, conditions, reservation discharge and appeal status.

Nozay PAR3: inquiry conclusions and reasoned opinionsSource: 15 Feb 2026

Land-use zoning

Partial evidence

The inquiry assesses the project against zone UI rules; this is not building permission.

Sources & next check

Evidence reviewed 27 Sept 2026

Next check

Match the approved application boundary to the current PLU and amendments.

Nozay PAR3: inquiry conclusions and reasoned opinionsSource: 15 Feb 2026

Grid & import rights

Partial evidence

MRAe describes a proposed double 225 kV underground link of about 3.6 km from Escargot and reinforcement at Les Loges. The 250 MW connection request is distinct from IT load.

Sources & next check

Evidence reviewed 27 Sept 2026

Next check

Obtain the connection agreement and updated reinforcement/energisation milestones.

MRAe: Nozay campus environmental opinion APJIF-2025-091Source: 8 Oct 2025

Ownership & development control

Partial evidence

The inquiry states DATA4 NOZAY SAS acquired 229,563 m², versus a 125,199 m² application footprint. Nokia retains occupation of other areas.

Sources & next check

Evidence reviewed 27 Sept 2026

Next check

Verify title, retained occupation and rights over the application area.

Nozay PAR3: inquiry conclusions and reasoned opinionsSource: 15 Feb 2026

Land, footprint & access

Partial evidence

MRAe records demolition of former Nokia buildings during August 2024–May 2025. Demolition is not commencement of the proposed data halls.

Sources & next check

Evidence reviewed 27 Sept 2026

Next check

Verify cleared-site conditions, boundaries and access arrangements.

MRAe: Nozay campus environmental opinion APJIF-2025-091Source: 8 Oct 2025

Flood, ground & environment

Partial evidence

MRAe calls for stronger assessment of noise, combustion emissions, ground conditions and ecology. Its environmental opinion is not an operating authorisation.

Sources & next check

Evidence reviewed 27 Sept 2026

Next check

Reconcile responses with final environmental conditions and monitoring.

MRAe: Nozay campus environmental opinion APJIF-2025-091Source: 8 Oct 2025

Water, cooling & heat

Partial evidence

The design includes closed-loop glycol liquid cooling and heat recovery. Proposed heat output exceeds the nearby housing demand evaluated; an offtake agreement is not established.

Sources & next check

Evidence reviewed 27 Sept 2026

Next check

Check final cooling/water balances and committed heat recipients.

MRAe: Nozay campus environmental opinion APJIF-2025-091Source: 8 Oct 2025

Programme & delivery

Partial evidence

The inquiry says the October 2025 start programme requires revision; preparatory authorisation was not established.

Sources & next check

Evidence reviewed 27 Sept 2026

Next check

Find a dated post-inquiry programme and evidenced commencement.

Nozay PAR3: inquiry conclusions and reasoned opinionsSource: 15 Feb 2026

Not assessed

Fibre & dark fibreDemand & location fit

Evidence still needed

Fibre & dark fibre
No verified site entry, dark-fibre offer or physically diverse route assessment is recorded. Regional coverage alone is insufficient.
Demand & location fit
Customer geography, latency, cloud or exchange nodes and a supported use case need project-specific evidence; national growth alone is insufficient.