Index methodology

Right-of-reply log

Every operator or facility we assess is offered a right of reply before — and after — publication, per the methodology's scoring rules. This page lists everyone we've contacted, when, and where things stand. It updates as responses arrive or deadlines pass; nothing here is final until an operator's own status says so.

Operator Sites covered Sent Deadline Status
Verne Keflavik campus 23 July 2026 6 August 2026 No response received — finalized
Green Mountain SVG-Rennesøy (Stavanger); TEL-Rjukan (Telemark); OSL-Enebakk (Oslo); OSL-Hamar (TikTok campus) 21 August 2026 4 September 2026 Responded 27 August 2026
Aker Nscale (JV) [1] Narvik 21 August 2026 4 September 2026 Pending
Bulk Infrastructure N01 Campus, Vennesla/Kristiansand; OS-IX, Oslo 21 August 2026 4 September 2026 Pending
Lefdal Mine Datacenter Lefdal Mine, Måløy 21 August 2026 4 September 2026 Pending
Nscale Glomfjord (Arctic Circle) 21 August 2026 4 September 2026 Pending
Skygard OSL1 (Hovinbyen), Oslo; OSL3 (Grorud), Oslo; OSL5 (Lørenskog) 22 August 2026 4 September 2026 Pending
STACK Infrastructure OSL03A, Fetsund; OSL03B, Fetsund; OSL03C, Fetsund; OSL03D, Fetsund; OSL04 Holtskogen, Tomter; COP02, Copenhagen 22 August 2026 4 September 2026 Pending
Vaultica OSL01 Ulven, Oslo; OSL02 Trollåsen, Oslo; COP01A, Copenhagen; STO01A, Stockholm (Upplands Väsby) 22 August 2026 4 September 2026 Pending
Blix Solutions BDC (Lindeberg), Oslo; NR5 (Rommen), Oslo; CJH, Oslo 27 August 2026 10 September 2026 Pending
  1. Contact was made via Nscale, the joint venture's operating partner — the email explicitly named Kristian Røkke as the appropriate contact for Narvik-specific questions. Aker ASA has not been approached separately about this joint venture.

A closed no-response entry is not a closed question. If Verne — or any operator on this list — gets in touch after their window closes, we update the assessment and this log together; the standing commitment holds regardless of the calendar.

A note on facility codes: several operators in this batch use near-identical short codes for entirely unrelated sites — Skygard's "OSL1", "OSL3" and "OSL5", Vaultica's "OSL01" and "OSL02", and STACK Infrastructure's "OSL03" and "OSL04" are all different facilities under different companies. Green Mountain shares the "OSL" prefix at two sites but does not number them: its own names are "OSL-Enebakk" and "OSL-Hamar", a region code plus a place. Every code in our facility pages and this log is paired with a place name and an operator; treat a bare "OSL0x" code you see elsewhere as ambiguous until you confirm which company it belongs to. Corrected 28 Aug 2026: this note previously gave "OSL1-Enebakk" and "OSL2-Hamar" as Green Mountain's codes. The numbers were ours, assigned in error — so we were partly warning about a collision we had created.