STACK Infrastructure — OSL04 Holtskogen, Tomter
PRE-REVIEW DRAFT — right of reply sent 22 August 2026, pending until 4 September 2026
Norway · Operational + expandable
| Status | Operational + expandable |
|---|---|
| Capacity (MW) | 18 (campus, four buildings) Sources: www.datacenters.com |
| Power source claim | UNVERIFIED |
| Published PUE | UNVERIFIED |
| Ownership / jurisdiction | STACK Infrastructure (Blue Owl Capital, USA, via IPI Partners) — RESOLVED 21 Aug 2026: this site stayed with STACK, not Vaultica, in the 2025 Apollo carve-out. Evidence: the Brønnøysund/Skatteetaten ownership chain (Infrastructure Nordics 2 S.à.r.l -> Infrastructure Nordics 3 AS -> Infrastructure Nordics 4 AS -> Infrastructure Norway I AS -> Si Osl 03.1, Si Osl 03.2, Si Osl 04, Si Osl 04.2, Si Osl 05.2, Si Osl 06, and Stack Infrastructure Norway AS) shows no OSL01/OSL02 entity; stackinfra.com lists only OSL03 (Fetsund) and OSL04 for Oslo; vaultica.com/norway/ lists only OSL01 and OSL02. See the OSL03 campus entries for the paired site. Sources: www.stackinfra.com · vaultica.com |
| AI / GPU relevance | UNVERIFIED |
| Verification notes | RESOLVED 21 Aug 2026 (see ownership field) — supersedes the earlier UNVERIFIED-OWNERSHIP flag. The ultimate parent Infrastructure Nordics 2 S.à.r.l is not independently confirmed as now Blue Owl-controlled (presumed, since Blue Owl's IPI acquisition closed Jan 2025 and a holding entity's name would not necessarily change) — asked directly in right-of-reply. Entities Si Osl 05.2 and Si Osl 06 in the registry chain suggest possible additional OSL05/OSL06 sites — not creating pages for these; recorded as an open question pending STACK's reply. Right of reply sent 22 Aug 2026; response window open until 4 Sep 2026. CODE COLLISION NOTE: 'OSL04' does not currently collide with another operator's code in this dataset, unlike its OSL01-OSL03 siblings in this cluster -- still worth reading together with the operator name as a matter of habit given how many operators reuse this numbering pattern. |
Fields marked UNVERIFIED could not be confirmed against a public source. We publish uncertain data as uncertain.