Vaultica — COP01A, Copenhagen
PRE-REVIEW DRAFT — right of reply sent 22 August 2026, pending until 4 September 2026
Denmark · Operational
| Status | Operational |
|---|---|
| Capacity (MW) | 1.2 MW IT load, ~4,600 m² white space across three floors (Denmark page) vs 800 kW (Nordic region page) — Vaultica's own site gives two different figures for this site; both shown, neither picked. See the Vaultica assessment for this as a recurring pattern, not an isolated error. Sources: vaultica.com |
| Power source claim | 100% certified renewable hydro and wind energy (operator claim) Sources: vaultica.com |
| Published PUE | UNVERIFIED — no PUE published on Vaultica's current site |
| Ownership / jurisdiction | Apollo Global Management (US), via Apollo-managed infrastructure funds — same ownership chain as Vaultica's Oslo sites (OSL01/OSL02): IPI Partners to Blue Owl Capital (closed 6 Jan 2025) to Apollo carve-out of STACK's European colocation business (announced 29 Apr 2025, closed 13 Aug 2025), relaunched as Vaultica. History confirmed on Vaultica's own site (vaultica.com/denmark/, page updated 4 Aug 2026): operated as STACK COP01 until August 2025; originally DigiPlex Copenhagen. Sources: www.apollo.com · vaultica.com |
| AI / GPU relevance | Enterprise/hyperscale colo; AI relevance UNVERIFIED |
| Verification notes | Added 22 Aug 2026 — dataset previously conflated this site with a generic 'STACK Infrastructure Copenhagen' entry; the two are in fact separate facilities under separate current owners (see STACK COP02 entry, same country). Location: Holmbladsgade 142, 2300 Copenhagen (corrected spelling, 22 Aug 2026). Certifications reported: ISO 14001, ISO 27001, ISO 50001, ISO 9001, PCI DSS, SOC 1 Type 2 (operator-reported, not independently audited by Greenpool). COP01 capacity discrepancy added to the right-of-reply follow-up list for Vaultica, alongside the existing OSL01 conflict. Right of reply sent 22 Aug 2026; response window open until 4 Sep 2026. |
Fields marked UNVERIFIED could not be confirmed against a public source. We publish uncertain data as uncertain.