Reconciliation ยท dataset 2026-08-18
Three figures, one market, counted three ways
The same jurisdiction produces different totals depending on what is being counted. Rather than pick one and hide the others, every headline figure on this site states its own scope. These sets are not equal on purpose.
Alberta, filed with the system operator
Data-load entries only. Industrial transmission load on the same AESO list is excluded.
21.4GW
Filed in total
42 entries
1.8GW
Has a connection date
13 entries
19.5GW
Has no connection date
29 entries
The two parts add back to the total, so this page can be checked against AESO's own file.
The figures here are transcribed from AESO's published connection list and reproduce from the source file. Capacity is the sum of a project's energization stages, EN1 through EN3, not the first stage alone: a project filed at 400 MW in EN1 and 400 MW in EN2 counts as 800 MW.
This edition against the last
AESO replaces the list monthly. Holding 2026-07 against 2026-08 gives the change, which is a difference between two published files rather than an estimate.
- Entered +1,800 MW 1 entry
- Left None 0 entries
- Net change +1,800 MW 21,365 MW across 42 entries
Entered minus left does not always equal the net change, because a capacity figure on an entry that stays in the list can also be revised between editions.
Why the tracked figure is smaller
9.8GW
announced in Alberta, not yet operating
20 tracked Alberta projects
This is the jurisdictions page figure, and it counts a different set from the queue. It is our own compilation: projects with a named proponent and a dated public source, whether or not they have filed with AESO.
It comes out below 21.4 GW because AESO publishes a project name and a load but never the applicant. Of 42 filed entries, 12 are matched to a named Alberta project in this dataset. The rest are real filed capacity with no public company attached, so they count in the queue and cannot appear in a list of tracked projects.
The two are never added together. A company saying 400 MW and a company asking a grid for 400 MW are different events, and some projects are both.
The rest of the dataset
- 12.9 GW
- announced in Canada, not yet operating, across 50 projects
- 491 MW
- energized in Canada, across 17 sites. A further 6 sites are operating but publish no capacity, so they add nothing to this figure. The true energized total is higher.
- 416 days
- median in-service slip, across the 11 filed entries that have moved a date. Accumulated across all of them the total is 13.5 project-years, which is a sum over separate projects and not the delay on any one of them.
- 7 of 49
- references seen since the first edition that have since left the list
What counts, and what does not
- Data-load only
- AESO marks each row with an MW Type. Only rows marked Data Load are counted. Industrial transmission load on the same list is excluded, so the filed figure is not the size of Alberta's whole large-load queue.
- Crypto-mining sites are in scope
- Sites built for proof-of-work are counted alongside AI and cloud. They draw the same power, occupy the same interconnection capacity, and several are converting to compute. Where a site is mining rather than AI, the project page says so.
- Announced and filed are never summed
- An announcement and an interconnection request are different events. Some projects have one, some the other, some both.
- Counted without being drawn
- A project with no disclosed location still has its capacity. It counts in every total and is not placed on the map rather than being guessed at a town centroid.
- Capacity is the sum of energization stages
- AESO files load in stages, EN1 to EN3. A figure here is the sum across stages, not the first increment, which is why some entries read higher than a single column of the source workbook.