Scrutica
Supply Chain
Power capacity, hardware inventory, upstream suppliers, and downstream customers for the row owned by Tencent Holdings Ltd.; any BIS Entity List exposure is walked through the canonical org graph rather than asserted at the facility row.
Capacity, ownership chain, and supply-chain position for Tencent Tianjin Cloud Data Center, including any export-control exposure that surfaces when the BIS Entity List touches a node above the facility in the chain.
As of 2026-07-06
Operator (or owner of record) per the Scrutica facility row.
Tencent Holdings Ltd., the documented owner of Tencent Tianjin Cloud Data Center, sits as a seed node in 1 pre-built cascade scenario. Severity is the scenario's seed-impact value (per-node override where one is defined); decay reflects the curator's substitutability assessment for the disrupted role. Run any scenario to walk the propagation through the full supply-chain graph.
Upstream dependency on US tools (EDA, advanced equipment, foundry access) is structural for Chinese AI compute consumers — domestic substitutes exist but cover narrow node ranges, so impact propagates with little dampening per hop.
Description
Tencent's first fully self-built super-large data center, hosted in the Tianjin Binhai High-tech Industrial Park area. Initial 40,000 m² footprint with capacity for ~200,000 servers, operational from 2010 per Tencent corporate communications (tencent.com/en-us/articles/80082). Anchors Tencent's Beijing-Tianjin-Hebei (京津冀) compute hub-node footprint per the Chinese government's "Eastern Data Western Compute" (东数西算) eight-hub strategy referenced in Tencent investor communications. Subsequent build-out at the Tianjin High-tech Zone announced as the Tianjin High-tech Cloud Data Center extension (Idcnova-Media reporting).
Timeline
Operational
Jan 1, 2010
Notes
authority_tier=2: facility existence + 2010 operational date + 40K m² / 200K-server initial scale anchored to Tencent corporate page (tencent.com/en-us/articles/80082); LEED V4 O+M Platinum certification cross-referenced via Tencent ESG materials. Per-facility MW capacity NOT disclosed. Coordinates NULL — site is in Tianjin Binhai high-tech zone but facility-precision coordinates not disclosed in primary source.
Other Tencent Holdings Ltd. Facilities
Parent / controlling entity, documented through a public filing or LEI registry.
Source: HKEX / SSE public filing · Confidence HIGH
Chain terminates at a publicly-listed entity (MIH Internet Holdings B.V.). Subsequent ownership is observable via SEC filings or the equivalent national registry.
China (CN)
Not a Wassenaar participant; operates its own Export Control Law (2020) and Unreliable Entity List; MOFCOM and the Ministry of Commerce administer dual-use catalogues.
Regimes: Chinese Export Control Law (2020); MOFCOM Unreliable Entity List authority
Established via: Tencent Holdings Ltd.
Netherlands (NL)
Operates the EU dual-use framework plus discrete national export rules on advanced semiconductor manufacturing equipment (DUV/EUV) introduced in 2023.
Regimes: Wassenaar Arrangement; EU Dual-Use Regulation 2021/821; Dutch national semiconductor-equipment rules
Established via: MIH Internet Holdings B.V.
No flags found across the chain (BIS Entity List, designation-cascade closures, or compute-threshold reporting obligations) as of 2026-07-06. Cascade closures evaluated: 0.
No ownership-change events documented in the available data for any entity in this chain over the last 5 years. Events draw from a licensed corporate-ownership database’s deal records (M&A, buyout, divestiture, asset sale, JV formation); 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.
China Development Bank Capital
CDB is associated with China’s China: National AI Programs / Big Fund III / Eastern Data Western Computing. See actor profile →
Touches Tencent Holdings Ltd. (chain hop 1) via a private-market fund. Commitment dollar value not disclosed (2012-03-01).
Mubadala Investment Company
Mubadala is associated with United Arab Emirates’s UAE: Stargate UAE / G42 / Core42 / TII Sovereign AI + Microsoft Cumulative + Abu Dhabi Digital Strategy. See actor profile →
Touches Tencent Holdings Ltd. (chain hop 1) via a private-market fund. Commitment dollar value not disclosed.
The walk for Tencent Tianjin Cloud Data Centerstarts at the operator org id (or owner org id when no operator is recorded) and climbs upward through the unified affiliate graph, normalized to trace child-to-parent relationships. At each hop, the highest-authority parent edge wins (priority ordering: SEC EDGAR / 10-K / LEI registry > licensed corporate-ownership database > licensed supply-chain database > BIS / Federal Register > licensed affiliate graph). 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 (licensed corporate-ownership database): 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 the database'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 the underlying data 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 ingested sources but are not surfaced on this card. And some licensed-database 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-07-06. Walk depth observed: 2 hops. Sources combined: Scrutica facility record + licensed corporate-ownership database + SEC CIK cross-reference + LEI registry + (where applicable) licensed supply-chain database + Federal Register designation closures. The licensed databases are held under subscription and not redistributed; per-hop labels name no vendor.
4
CN