Vitreous LabsEnergy transparency
Great Britain · the operating fleet

Whitegate

58 MW in Great Britain. Everything on this page is read from published data for the 364 days to 16 October 2026, or is labelled as an estimate.

Added automatically on 2 October 2026. Elexon's register lists this unit as a battery and the settlement archive shows the control room accepting bids or offers from it from 30 September 2026. Its location, owner and trader have not been checked yet, so it is not on the map and carries no owner. It is on the weekly fleet log to be checked.

What it is

Registered power58 MW balancing mechanism registration
Balancing mechanism unitT_WTGTB-1

Who owns it and who trades it

Traded byHD144WHI Ltdconfirmed, Elexon's register
Owned bynot published anywhere we can read

Market registers name the party that sells into the market, which for a battery is usually an optimiser under contract rather than the owner. Elexon's balancing mechanism unit register names the seller here and the name is checked against it on every build. How we tell them apart

What it earned

Line364 days to 16 October 2026
Balancing mechanism−£127k
Response and reserve auctions auction implied£0
Capacity marketno agreement we can attach
Three lines togethernot netted

Balancing is offer revenue and does not net off the cost of the power. The response and reserve figure is the value implied by the published auction results, award quantity times clearing price times the length of the delivery window, and not a settled payment. Capacity market income is the cleared price raised for inflation where the auction set a base period, split by month on EMRS's weights. Method

Outside the balancing mechanism, derived from the meter

Elexon publishes what this unit's meter recorded every half hour. Take away the balancing volumes NESO accepted and what is left is the position the unit ran outside the balancing mechanism: its wholesale trading, its frequency response delivery, and its losses, together. This unit held no frequency response contract in the window, so the whole position is treated as traded. The volumes are measured. The prices are public benchmarks, not this unit's trades. The product is derived, and is shown apart from the three measured lines above. 107 days to 11 October 2026, 45 of them still provisional in Elexon's settlement runs. Method and caveats

LineMWh or £
Metered export, what crossed the meter out3,639 MWh
Metered import, what crossed the meter in4,724 MWh
Equivalent full cycles, everything sent out over one full charge·
Apparent meter to meter efficiency77%, plausible: losses plus a standing load that is material against a modest throughput
Balancing offers accepted1,057 MWh
Balancing bids accepted1,826 MWh
Position outside balancing, export4,359 MWh
Position outside balancing, import4,674 MWh
Valued at the market index, sold£715k
Valued at the market index, bought£494k
Outside balancing, net, at the index£221k
Balancing and outside balancing together£131k £7.73/kW/yr

When it moved, against when power was dear

Across every half hour this unit was metered the market index averaged £121.90. What it sent out was worth £163.98 a megawatt hour at that same index, 1.34 times the average. What it took in was worth £105.74, 0.87 times. Selling above one and buying below one is a unit positioned into the dear half hours and out of the cheap ones. It measures the half hours it chose, not the price anyone paid it, which is not published.

What it paid to buy energy back

When NESO accepts a bid, this unit delivers less than it had already sold, or takes more in. It pays for the energy it no longer delivers, and that payment is most of what makes the balancing figure above negative. Whether that is a cost or a margin depends on the price it paid. Across 1,826 MWh of accepted bids it paid an average of £126.17 a megawatt hour. The market index averaged £178.26 across those same half hours, so it bought back at £52.09 a megawatt hour below the going price.

Price it paidVolumeAverageCash
below zero23 MWh−£10.43£241 received
£0 to £256 MWh£15.22£91
£25 to £5034 MWh£32.08£1k
£50 to £751 MWh£74.00£100
£75 to £100442 MWh£90.55£40k
above £1001,319 MWh£143.46£189k

On 23 MWh the price was below zero: NESO paid this unit an average of £10.43 a megawatt hour to take energy, £241 in all. That is a constrained network with more generation on it than it can move.

The other direction, offers, is much smaller here: 1,057 MWh where NESO asked for more, paid at an average of £133.68 against an index of £91.19.

Checks this unit did not pass cleanly. Published anyway, because a flagged figure with its flag is more use than a blank.

  • only 107 of 364 days metered

Where it stands

All three measured lineswhole fleet, £/kW/yr11th percentile230 units

Percentiles, so 90 means better than nine in ten of the cohort named beside it, on that measure alone, over the same 364 days. Rates are pounds per kilowatt per year, annualised over the days the unit has been on the system, the same figures the performance league ranks on. A high position in the taken-in table is not a fault: a constraint asset is paid to charge, and charging is its job.

The nearest comparables

The five nearest in size in England and Wales, and this battery among them, ranked by what each was paid for every kilowatt it holds over the 364 days to the same date. How long this battery can run for is not published, so duration is not used to choose them. Same market, same rules, same weather.

BatteryMWHoursMeasured, per kW
Ocker Hill582h£63.1/kW/yr
Monk Fryston572h£43.8/kW/yr
Sizing John572.5h£41.5/kW/yr
Capenhurst572h£26.9/kW/yr
Native River572h£20.0/kW/yr
Whitegatethis battery58not knownnot netted

The three lines are not added together for this site. It paid £313k to charge and the lines we can measure paid it £185k. The energy it bought was sold in the wholesale market and nothing published measures that sale, so subtracting one from the other would show a loss it does not make.

See it on the map

Open the operating map here

Every figure on this page traces to a published file. If something here is wrong about your asset, the methods section says how to tell us.