How the queue data is built, and where it stops being a fact
The rule throughout is that data which is absent is never invented. Where something is inferred it is labelled, drawn differently, and explained at the point of use.
The register
One row per project identifier. Capacity is the sum of the register's own MW increase or decrease, which is new capacity only. Cumulative total capacity is deliberately not used, because it equals connected plus increase and therefore counts plant that is already standing at a brownfield site. Using it would inflate the pipeline from 426.7 GW to 438.3 GW.
Coordinates, and four grades of them
The register names a connection site on every row and publishes no coordinate for any of them. Four routes, in descending confidence:
| Grade | How |
|---|---|
| published | NESO's own grid supply point and node lookup, matched on the site name. |
| name | The distinctive words in the name identify exactly one mapped substation, and every candidate for that name sits within six kilometres. |
| adjacent | The name carries a qualifier over an existing substation, Norton East or Wylfa South, and the base name resolves uniquely. |
| place | The name is a settlement, and that settlement is within 25 kilometres of the network at the stated voltage. Drawn with a dashed edge. |
A fragment of a name is never a match. An early version placed six unrelated sites at one coordinate because it matched on the word bess after stripping farm, and another matched Botley West to Botley Wood. Both rules were deleted rather than tuned. A multi word name has to find a multi word match, and a directional qualifier the candidate does not share is a rejection.
The connection point score
Four components with stated maxima, then a deliverability gate. Contested out of 40 is all storage capacity seeking the point, against the largest stack in the country. Returning on evidence out of 30 is Gate 2 capacity whose contracted date has already passed. Returning on risk out of 20 is Gate 2 capacity scoring high on delivery risk but not yet late. Persistence out of 10 asks whether more than one applicant is present, so churn is not a single counterparty event. The total is multiplied by 1.0 where storage is already energised at the point, 0.8 where Gate 2 is present and consented, 0.5 where Gate 2 is present with nothing consented, and 0.25 where there is no Gate 2 position to take.
Delivery risk
Consent gap out of 50, days past the contracted date out of 30, capacity scale out of 20. The lead times behind the consent gap, 1,095 days from scoping, 730 from awaiting consents, 547 from consented and 180 from under construction, are inference and are published nowhere. They are stated so you can disagree with them.
Ownership
Applicants are grouped into platforms by shared registered address at Companies House, which is strong but circumstantial evidence of common control, and it is graded. An address only groups where fewer than five hundred companies are registered at that postcode. Fifteen postcodes in this set host more than a thousand companies each and one hosts over seventy thousand, so a shared address there means nothing and those applicants are left ungrouped.
Balancing mechanism revenue
Every accepted bid and offer for 364 days, taken from Elexon's settlement stack, aggregated by unit. Validated against NESO's published balancing cost at a ratio of 0.97 for a sample three days before any figure was used. Offer revenue is reported because it is unambiguous. Net balancing cash is not profit and is not presented as such.
The distribution queue
Batteries that connect at 132 kV and below apply to their distribution network operator, not to NESO, and each of the six operators lists them in an embedded capacity register. The Atlas layer draws every battery of 1 MW and over that a register shows as accepted to connect, at the position the operator gives for the site.
Some of these batteries also hold a transmission agreement, so they are in NESO’s queue as well. The registers and NESO share no project identifier, so each battery is compared with the queue in order of strength of evidence, and each queue row can be used once.
| Drawn as | Test |
|---|---|
| in it, by company | The register’s customer and the queue’s applicant are the same company by name, the same size within 15%, at the same supply point or within 15 km. The size may be the queue’s battery or its whole connection, because a hybrid park’s register entry can give either. |
| in it, by site name | A distinctive word of the site name is in a queue project’s name, within 10 km, the same size within 10%. |
| unclear | A queue project of the same size at the same supply point; or one at a planned node with no published position, in the same transmission area and node region, sharing a site word; or anything the Atlas holds within 3 km. None of these is counted as held. In a sample of twelve same size, same supply point pairs read by hand on 1 November 2026, three were the same battery. |
| not in the transmission queue | None of the above. |
Read by hand on 1 November 2026, the comparison had gone wrong in four ways, and each is now closed. A queue project at a planned node with no position, Hunterston in Ayrshire, was taken for a battery in Yorkshire called NEL Hunter. Fiddlers Ferry was read as Ferrybridge. One company’s four 50 MW batteries round Glasgow were each paired with another’s queue row. And a hybrid park whose register entry gave its whole 240 MW connection was missed, because the queue gave its 117.6 MW battery.
Every battery, linked
Each battery in the registers, accepted or connected, is then linked to every other record the site holds about it. Each link says what it rests on, and a link the rules do not settle is shown as possible or left out, never promoted.
| Link | How it is made |
|---|---|
| Company | The register’s customer, found at Companies House in its free monthly snapshot of every live company: by its name, by a former name, with “Limited” added where the register left it off, or in full where the register cut it short. A name that fits several companies, a single bare word, a placeholder, or a bare name whose only match is in an unrelated trade (“Washington Services”, a motorway service area, found a road haulier) is not taken. Northern Powergrid prints the site name where the customer should be, so for its batteries the company comes from the queue project or capacity market unit the battery is firmly linked to, and the page says so. A consultancy that applied on an owner’s behalf is shown as such and is not read as the owner. |
| Developer | The transmission queue’s own attribution for the same company number; else a parent the company itself named in its own capacity market application; else a registered office shared only with queue companies of one developer. That last one is graded as a lead, because an office records who set a company up, which is not always who owns it now, and past 20 companies at one postcode, or at an address care of someone else, the developer must also be in the company’s name. |
| Gate | Northern Powergrid publishes one row per project with its transmission gate, matched here on supply point, size and acceptance date. UK Power Networks publishes the batteries at each supply point by gate, not one by one, so a battery’s gate is set only where those figures leave a single answer, and otherwise the supply point’s mix is shown beside it. |
| Capacity market, planning, operating unit | Firm: the same company; a distinctive site word in common nearby, at about the same size; or the same place and size, where the battery’s position is its own. Possible: within 1 km and of a similar size, which at a busy substation can be a neighbour; a unit connecting to the transmission system; a unit held by a different company from the battery’s own. A unit trading at the site of a battery still accepted to connect is shown as operating at the same site, an extension or a later phase. |
Four rules keep the links honest, each added after an independent check on 1 November 2026 found links it could break. A battery’s own supply point is not a site word: “Walpole Bank East” at Walpole shares that word with every project at the substation, which says nothing. A battery named after its substation still matches, but only within a kilometre at about the same size, or, for the queue, only where one battery and one queue row fit each other and nothing else. A position shared with another battery, or given to about a kilometre, cannot make a distance test firm: SSEN gives one grid reference to six batteries round Abernethy. A record can be firmly the same as one battery only; where several claim it, the strongest keeps it, a connected battery before an accepted one, and where the best two cannot be told apart neither does. And an aggregator, an agent, a solicitor or the network operator holding a capacity market unit or a queue row is never read as the owner or the developer.
The way back works too: a queue project, a capacity market unit, a planning record and an operating battery each say when a distribution register holds the same battery, and an asset page carries what its register says about it.
So the green count is an upper bound. On the same date 99 of the batteries drawn green, 4.2 GW, shared only a common word such as street or manor with some queue project, and a few of those may be the same battery under another name. The registers are read every Monday and every edition is kept, so a battery that joins, leaves, connects, changes size or changes hands is recorded from the edition it appears in.
What is refreshed, and when
The connection registers are read on Tuesdays and Fridays and compared with the previous capture, so entries, exits, gate moves, capacity changes and applicant changes are recorded rather than reconstructed. The six distribution registers are read on Mondays. The capacity market, planning and Companies House sets refresh on their publishers' own cycles, which the tool states next to each.
Every source, when it was last read, and under what licence
This table used to live inside the tool, where it reappeared in a 350 pixel column beside a map that has nothing to do with it. It belongs here, where it can be read once.
| Source | As at | Refresh | Licence |
|---|---|---|---|
| NESO transmission entry capacity and embedded registers | 13 November 2026 four days ago | twice weekly | NESO Open Data Licence |
| NESO connections reform results databook and existing agreement register | January 2026 11 months ago | one off | NESO Open Data Licence |
| NESO thermal constraint costs | August 2026 4 months ago | monthly | NESO Open Data Licence |
| NESO capacity market register | 19 August 2026 3 months ago | continuous | NESO Open Data Licence |
| NESO TNUoS generation tariffs, 2031 forecast | 11 May 2026 6 months ago | annual, with forecasts | NESO Open Data Licence |
| NESO grid supply point and node lookup, ETYS boundaries, licence areas | February 2026 9 months ago | irregular | NESO Open Data Licence |
| Companies House basic company data | 1 August 2026 4 months ago | monthly | Open Government Licence |
| Renewable energy planning database | Q2 2026 5 months ago | quarterly | Open Government Licence |
| OpenStreetMap power network, Geofabrik extract | 19 August 2026 3 months ago | daily | Open Database Licence, share alike |
| Natural Earth neighbouring land | 10m release | irregular | public domain |
| OpenStreetMap power substations, Geofabrik extract | 19 August 2026 3 months ago | monthly | Open Database Licence, share alike |
| Elexon balancing mechanism unit registry | 17 November 2026 today | monthly | Elexon open data, free reuse with attribution |
| GeoNames Great Britain settlement gazetteer | 20 August 2026 3 months ago | monthly | Creative Commons Attribution 4.0 |
| Elexon settlement stack, every accepted bid and offer for 364 days | 15 November 2026 two days ago | daily | Elexon open data, free reuse with attribution |
| National Grid Electricity Distribution, embedded capacity register | August 2026 | read every Monday | NGED Open Data Licence |
| Northern Powergrid, embedded capacity register | 13 November 2026 four days ago | read every Monday | Northern Powergrid Open Data Licence v1.0 |
| SP Electricity North West, embedded capacity register | 20 October 2026 28 days ago | read every Monday | CC BY 4.0 |
| SP Energy Networks, embedded capacity register | 9 October 2026 39 days ago | read every Monday | CC BY 4.0 |
| Scottish and Southern Electricity Networks, embedded capacity register | October 2026 | read every Monday | CC BY 4.0 |
| UK Power Networks, embedded capacity register | 13 November 2026 four days ago | read every Monday | CC BY 4.0 |