Scrutica
Supply Chain
Not yet available
Facility-level telemetry including power capacity, hardware deployments, supplier relationships, and downstream dependencies. Linked to NTT DATA's Global Data Centers division with cross-referenced BIS Entity List matches.
Detailed intelligence on NTT Jakarta 3 Data Center (JKT3). Tracks operational capacity, ownership structure, and the facility's strategic position within the global AI supply chain, including relevant export control restrictions.
As of 2026-04-27
Direct operator or owner of this facility per the Scrutica facility record.
Ownership chain not yet documented in available substrate (PitchBook affiliate graph, FactSet supply graph, SEC filings, LEI registry; as of 2026-04-27). The chain may extend further once additional ingestion runs complete; absence here reflects substrate coverage at this snapshot, not a documented apex.
Notes
Other NTT DATA's Global Data Centers division Facilities
No jurisdictions documented in this chain’s available substrate — at least one ancestor must carry an HQ country in the canonical organization record for jurisdictional exposure to compute. Once entity-resolution backfills add HQ countries to the chain, this section will populate automatically on the next refresh.
No flags found across the chain (BIS Entity List, designation-cascade closures, or compute-threshold reporting obligations) as of 2026-04-27. Cascade closures evaluated: 0.
No ownership-change events documented in Scrutica’s available substrate for any entity in this chain over the last 5 years. Events draw from PitchBook deal records (M&A, buyout, divestiture, asset sale, JV formation); PitchBook coverage is strongest for private US/EU transactions and partial for state-owned-enterprise restructurings or non-Western private deals. Subsequent ingestion runs may add events here.
No documented sovereign or state-linked LP investment touches any entity in this chain. PitchBook LP-disclosure rate is partial; absence of evidence here is not evidence of absence.
The walk for NTT Jakarta 3 Data Center (JKT3) starts at the operator org id (or owner org id when no operator is recorded) and climbs upward through the unified affiliate graph (ownership_chain_edges), normalized child→parent via the ownership_upward_edgesview. At each hop, the highest-authority parent edge wins (priority ordering: SEC EDGAR / 10-K / LEI registry > FactSet Workstation / Revere > Compustat > BIS / Federal Register > PitchBook). Confidence and recency break ties.
The walk terminates on (a) a node with a public-filing-grade ancestor edge — a SEC filer, an LEI-registered listed entity, or a 10-K-disclosed parent — (b) a government entity, (c) a 10-hop limit, or (d) a detected cycle. When termination is not at a public filer or government, the panel labels the chain's end-state as opaque beyond that point. Opacity is reported, never implied.
Per-source confidence (PitchBook): HIGH for Parent / Subsidiary edges; MEDIUM for JV and AFFILIATE edges. Known limitations: (1) shell companies with undisclosed principals terminate the public-record walk; (2) recent transactions reach the panel after PitchBook's weekly refresh; (3) cross-jurisdiction private holding structures may carry intermediate hops that are not in any ingested source. Each row carries an edge-level as of date so freshness is auditable per hop.
Two further caveats are inherent to how the walker and substrate compose. The walker selects a single highest-authority parent per hop, so JV or multi-parent ownership structures collapse to one displayed path; alternate parents exist in the substrate but are not surfaced on this card. And some PitchBook edges encode parent-of relations against entity-resolved stub IDs whose display name reflects a sub-entity (a business unit, an acquired-then-renamed line) rather than the canonical parent — when a chain reads structurally surprising, the per-row source citation is the authoritative reference, not the chain's narrative shape.
Computed at: 2026-04-27. Walk depth observed: 1 hop. Sources combined: Scrutica facility record + PitchBook affiliate graph + SEC CIK cross-reference + LEI registry + (where applicable) FactSet Revere supply-chain graph + Federal Register designation closures.
NTT Berlin 1 Data Center (BER1)
Berlin, Germany