Half Hour: downloads These files are the Half Hour record of GB Balancing Mechanism payments and three related ledgers, generated by the same export as the interactive site and the readable edition (/read/). Every figure in them is also in the JSON files under /data/, which carry the exact source requests and fetch times. Half Hour is independent. It is not affiliated with, endorsed by or produced by Elexon, NESO or Companies House. Figures are indicative. FORMAT UTF-8, a header row, LF line endings, comma separated, no thousands separators. Money is GBP: whole pounds in day, period and window totals; pence in half-hour cashflows and in auction-cleared value. Prices are GBP per MWh. Energy is MWh. TEXT THAT LOOKS LIKE A FORMULA Names come from outside data. A text value that begins with =, +, -, @, a tab or a carriage return is written with a leading apostrophe (') so that spreadsheets do not treat it as a formula. Removing the apostrophe gives the value as held. Numbers, including negative numbers, are never prefixed. How many cells were prefixed in each file is printed by the export each day. MISSING IS NOT ZERO An empty cell means no value is held. A recorded zero is 0. A unit with no row has no recorded acceptance, which is different from a recorded zero. THE CLOCK A settlement day is a UK local day. It has 46, 48 or 50 half-hour settlement periods (46 on the day the clocks go forward, 50 on the day they go back). Never assume 48. settlement_periods_in_day is the calendar's count; settlement_periods_held is the count the record holds. Period 1 starts at local midnight; period_start_utc is the start of the half-hour in UTC. Services use NESO's auction day (23:00 to 23:00 GB clock time), which is not a settlement day. THE MONEY MEASURES (Balancing Mechanism ledger) A cashflow is gross and indicative. It is never profit. Fuel, carbon, start-up and other costs are not deducted. offer_cashflow_gbp sum of accepted offer pair cashflows. Positive means the system paid the unit. It is one signed total per unit and half-hour, and a small part of it is negative. bid_cashflow_to_units_gbp sum of the positive bid pair cashflows: the system paid units to reduce output. bid_cashflow_from_units_gbp sum of the negative bid pair cashflows, a negative number: units paid the system. gross_received_gbp offer_cashflow_gbp + bid_cashflow_to_units_gbp. gross_paid_gbp minus bid_cashflow_from_units_gbp. net_bm_cashflow_gbp gross_received_gbp - gross_paid_gbp. Net is never shown alone and is never profit or loss. A negative net is not a commercial loss. The interactive site counts a unit's negative offer cashflow in gross paid rather than inside gross received, so its gross figures can differ from these by up to that negative part; net is the same either way. Year and month totals are sums of the unrounded cashflows rounded once, as the archive total in data/meta.json is. Adding the rounded rows of days.csv can differ from them by a few pounds. PRICES An offer price is not a wholesale price, and neither is a household tariff. The system price shown here is the imbalance price Elexon publishes for each settlement period (systemSellPrice in its system prices data); it is not the price any unit was paid. Every price on this page says which kind it is. system_sell_price and system_buy_price are Elexon's systemSellPrice and systemBuyPrice; net_imbalance_volume_mwh is its net imbalance volume; market_index_price is the APXMIDP market index price. They are different prices and are never interchangeable. THE REGISTERED LEAD PARTY The registered lead party (as registered now) is the party Elexon's register gives for a unit today. The feed attaches that one party to every historical row, so it is not the party registered on an earlier date. It is not necessarily the owner, the operator or the party that decides bids, and it is never called the owner here. Totals by lead party are payments to units currently registered to that party. TECHNOLOGY Technology classes come from the fuel type in Elexon's register. Where the register gives none, the class of a battery is inferred from the unit's name and is marked "inferred from the unit name" wherever it appears; it may be wrong. Units with no basis for a class are "Unclassified". technology_basis: register (Elexon register fuel type), name_inferred (inferred from the unit name, may be wrong), mixed (units of both kinds in the class), none (Unclassified). PROMINENCE Receiving a high price, or a large share of payments, is not evidence of wrongdoing. A large station receiving a large sum is the expected case and is consistent with ordinary operation of the market. Every ranking on this page is a ranking of the record and nothing more. FILES financial_years.csv, calendar_years.csv, months.csv period (financial years labelled like 2025/26, 1 April to 31 March); period_from, period_to (the whole period's dates); whole_or_part (part: only some days are held, and totals are for those days); calendar_days; days_held; first_day_held; last_day_held; settlement_periods_held; the six money columns; highest_system_price_gbp_per_mwh with its date and period. days.csv One row per settlement day held: settlement_date; settlement_periods_held; settlement_periods_in_day; the six money columns; highest, lowest and mean system price (the mean is unweighted over the day's periods) with the periods of the highest and lowest; units_paid_for_offers (units with offer cashflow above zero); unit_with_largest_offer_cashflow and largest_unit_offer_cashflow_gbp; top5_units_share_of_offer_cashflow (0 to 1); latest_fetch_utc (the latest fetch among the day's source requests). half_hours_YYYY.csv One row per settlement period of one calendar year, for the whole market: settlement_date; settlement_period; settlement_periods_held and settlement_periods_in_day; period_start_utc; the system sell and buy prices; the net imbalance volume; the market index price; offer_cashflow_gbp, bid_cashflow_to_units_gbp and bid_cashflow_from_units_gbp summed over every unit in the half-hour, to pence. An empty cashflow cell means no unit has a row in that half-hour. settlement_periods_held counts the half-hours for which Elexon's system prices data has a row. On the few days where that is fewer than the calendar's count, a half-hour with cashflow rows but no system prices row is still listed, with empty price cells; its period_start_utc follows from the clock (periods are consecutive half-hours from local midnight). Cashflow in such half-hours is in the day totals too. Gross figures are not given per half-hour: offer cashflow is a sum of signed unit totals there, so gross received and gross paid cannot be separated at market level. units.csv bmu (Elexon BM unit id); ngc_bmu (NESO's id); name; technology_class, technology_basis, technology_inferred_from_name; registered_lead_party_as_registered_now; generation_capacity_mw and demand_capacity_mw (the register's capacity, not what the unit could deliver on a day); gsp_group; in_current_register; first_date and last_date (days with a row). Then, for each window (all: the whole archive; d365, d90, d30: that many days ending on the last day held; their dates are in data/units.json), the six money columns, offer_mwh (derived accepted offer volume) and days_with_a_row. Empty window cells: no row in the window. Inside a window with rows the export writes a component with no recorded values as 0 (data/units.json does the same), so in these two files a 0 bid cashflow means none was recorded on the days the unit had rows. lead_parties.csv registered_lead_party_as_registered_now; units_ever_carrying_this_party; the same window columns. Payments to units currently registered to the party, not receipts of the party. technology_months.csv month; whole_or_part; days_held; technology_class; technology_basis; technology_inferred_from_name (yes, some or no); offer_cashflow_gbp; bid_cashflow_to_units_gbp. Sums of the daily figures by class in data/days_tech.json. Bid cashflow from units is not exported by class and day, so gross paid by class and month is not given here; data/tech.json gives it by class for each window. adjustments_days.csv The adjustments ledger (Elexon DISBSAD), the columns of data/adjustments/days.json: date; n_periods; identified (1 when every non-zero row carries a party and an asset id; ic_ and kind columns are empty on a day that is 0); total_cost and total_mwh (every adjustment action); ic_cost, ic_mwh (interconnector trades, net) and their in (into GB) and out (out of GB) parts; other_cost, fast_reserve_cost, stor_cost, lcm_cost, unknown_cost; n_high_price and high_price_cost (rows at or above 5,000 GBP per MWh); n_parties; fetched_utc; then per route cost_in, mwh_in, cost_out, mwh_out. Cost is signed: positive is paid by the system operator, negative is money it took in. MWh is signed: positive into GB. The trading party in a row is a counterparty to a trade, not an owner. These figures are never added to Balancing Mechanism figures. services_days.csv auction_cleared_value is the volume a unit cleared in NESO's daily response and reserve auctions multiplied by the clearing price and by the hours of the delivery window (MW x GBP per MW per hour x hours), summed over what is stated. It is the value cleared at auction, not an amount paid or received: what a provider was actually paid depends on delivery, availability, performance penalties and settlement that this data does not show. One row per auction day: auction_day; auction_cleared_value_gbp; units; results; then per product its value, average_mw (cleared MW-hours divided by the hours of that day's service windows) and units. Never called paid or received, never added to any other figure. system_costs_days.csv NESO's daily balancing costs and volumes by NESO's own categories, the constraint breakdown and the thermal constraint costs by boundary, the columns of data/system/days.json. cost_total is the sum of the six cost categories, computed by this project (NESO publishes no total). calendar_periods, cost_periods and volume_periods: a day with fewer periods than the calendar is understated. These figures must not be added to the Balancing Mechanism ledger or to the adjustments ledger, or to each other across datasets. They are largely the same Balancing Mechanism acceptances, and the same trades outside it, that those ledgers record, grouped by the system operator's reason for the action instead of by who was paid. Adding them would count the same money twice. Within this layer, the constraints category of the daily balancing costs, the cost columns of the constraint breakdown and the thermal constraint costs by boundary also overlap one another and are not additive. The files carry no provisional or final flag. NESO describes the settlement date of the daily balancing cost and volume files as 'The Payment Date in relation to an Initial Settlement Run', so those figures come from the initial run and may differ from later settlement runs. NESO says tags on constraint actions 'can occasionally be changed post event' and that the constraint breakdown is then refreshed. All figures are treated as provisional and subject to revision. This project fetches again whenever the portal's last-modified time of a file changes and keeps every earlier copy. TRACING A FIGURE Each settlement day's exact Elexon requests and fetch times are under sources in data/day/YYYY-MM-DD.json. The other ledgers carry theirs in data/adjustments/day/, data/services/meta.json and data/system/meta.json. LICENCES AND ATTRIBUTION Contains BMRS data © Elexon Limited copyright and database right 2026 Licence: Copyright: Licence to use BMRS open data, https://www.elexon.co.uk/bsc/data/balancing-mechanism-reporting-agent/copyright-licence-bmrs-data/ Supported by National Energy SO Open Data Licence: National Energy SO Open Data Licence v1.0, https://www.neso.energy/data-portal/neso-open-licence Companies House register data: Companies House states that it imposes no rules on how the information on the public register is used (https://www.gov.uk/guidance/companies-house-data-products). No Companies House licence term or attribution statement could be confirmed. Anyone who copies, publishes or adapts these files must carry these statements with them (see /ATTRIBUTION.txt).