Skip to content
GridCapacityAPI.com

nl_nbnl_tennet_gebieden

Capaciteitskaart elektriciteitsnet — TenneT congestion areas (tennetgebieden.csv)

Published by TenneT TSO B.V. · NL · Monthly

Archived, pending reviewpending_reviewHealthy

Per TenneT congestion area and target year (2026–2036): the HV network's existing transport capacity and the contracted peak need, plus the current queue, as published on the national capacity map.

What is withheld, and why

Every value from this source is withheld. The operator’s terms do not clearly allow us to redistribute its figures, and when signals conflict the more restrictive reading wins until the operator confirms otherwise in writing. Records are still listed — with capacity.value null, access.status "withheld" and a link to the publication — so you know the operator publishes something there.

The publication is still read and kept, because operators overwrite their files and a history not recorded when it happened can never be recovered. If reuse is cleared, customers get the history as well as the present.

Fail closed. The portal terms grant reuse on behalf of 'de Netbeheerders', defined as the six regional DSOs; TenneT is not among them, and the words 'TenneT' and 'commercieel' do not occur in the terms. TenneT's own reuse terms could not be read (tennet.eu serves a Cloudflare challenge and its robots.txt disallows AI agents). The rights-retention sentence mentions 'haar licentiegevers', a possible hook, but it grants nothing on TenneT's behalf. Fetched and archived so the history exists if TenneT or EDSN clears reuse; ask centraaldataloket@partnersinenergie.nl and TenneT.

Licence and rights evidence

Licence
Energie Dataportaal — Algemene gebruiksvoorwaarden (Open omgeving); TenneT's own terms unknown (opens the operator’s site)
Attribution
None required
Technical access
Yes
Commercial use
Not established
May be cached
Not established
May be redistributed
Not established
Derived data allowed
Not established

Evidence

Methodology

1 version(s)

Capaciteitskaart: TenneT HV transport capacity, contracted peak need and queue per congestion area

nl_nbnl_tennet_gebieden_v2 · vbrondata_documentatie.txt v2.0 (2024-11-20)

TenneT states, per congestion area on its HV grid and per target year, the maximum transport capacity the network can carry (total) and the transport capacity needed at peak for all existing transport agreements (contracted), and the queue of its own HV-connected customers (waitlisted, MW and unique requests). Same definitions as the DSO layer, a different grid level and a different operator's calculation.

Capacity basis
operator published
Network state
unknown
Binding
No
Additive across assets
No — do not sum these figures
The method accounts for
reserved: not stated · allocated: not stated · pre-reserved: not stated · pending requests: no
Comparability class
nl_capaciteitskaart_tennet_hv
Documentation
—

The operator’s own caveats

  • Indicative; no rights can be derived from it.
  • Figures refer to TenneT's HV level only; never add them to a DSO area's figures.
  • The end date of congestion can differ for parts of an area from the expected moment of the last required grid expansion (the operator's own info note, in details).

How the publication maps to the model

availability types
["total","contracted","waitlisted"]
binding
false
directions
["offtake","injection"]
firmness
["firm"]
geometry precision
none
includes reserved projects
null
non additive
true
notes
["One row per congestion area (congestiegebied, a name: the only key the file has, and the one the station file refers to) and target year. 22 areas; five are a single row holding only their name, without even a year (TenneT's 'niet rode gebieden', no congestion declared, no data shared), and are listed as areas without values.","aanwezige (the network's limit, 'total') and benodigde (the contracted peak need, 'contracted') vary by year: they are a forecast per target year, published with horizon target_year.","The queue (wachtrij MW, unieke_verzoeken count with variant 'requests') is the same in every year of an area wherever it is present, so it is the current queue repeated per row; it is published once, as a snapshot, with the years it appeared in (details.jaren). If the years ever disagree, each year is kept as published and the run says so.","A queue MW published for one to three parties (Hengelo injection: 350 MW, 3 requests) is kept and marked details.few_requests, as in the DSO file: the operators say such queues are withheld to avoid tracing individual requests.","The TenneT-layer queue holds only TenneT's own (HV-connected) customers; it does not overlap with the DSO layer's queue, which includes DSO customers blocked by TenneT congestion.","Offtake and injection congestion areas are different partitions (Hengelo and Zwolle Hessenweg exist for injection only), so an area may carry one direction only.","afname_beperking, afname_tso_limiet, opwek_beperking, opwek_tso_limiet, voorspelde_capaciteit_*, start, eind and kwartaal are undocumented and empty; a run reports them if they fill."]
spatial scope
congestion_zone
technologies
["generic_load","generic_generation"]
units
["MW","count"]

Query this source

curl "https://api.gridcapacityapi.com/v1/capacity/search?source=nl_nbnl_tennet_gebieden&limit=20" \  -H "Authorization: Bearer gc_live_..."