| >1MW renewal cash mark-to-market remains materially above the 0-1MW spread, evidencing an embedded-mark-to-market pool on the legacy lease book | ||
| Double-digit core FFO per share growth is delivered, not merely guided, from the 2026Q2 multi-year statement | ||
| Hyperscaler customers continue to lease wholesale capacity rather than substitute to self-build for incremental AI demand | ||
| The Blackstone / Teraco / Columbia Capital transactions deliver the meaningful accretion management guided to as starting next year (2026Q2) | ||
| The 2.7% weighted-average interest rate and 4.6-year weighted-average maturity do not reprice destructively inside the horizon | ||
| The fee-income stream (management, development/construction fees) is genuinely recurring rather than episodic, as characterised in 2026Q2 |
The revision tape is unambiguously positive — EPS 6 up / 0 down and revenue 9 up / 0 down over 365 days, breadth 1.0 on both, median revenue revision +7.0% — and velocity is rising (0.74 revenue moves per 30 days). My va | high |
My p_bull of 27% is 21.2pp below the node-pooled +30% base rate of 48.2%, and my p_bear of 25% is 6.3pp below the pooled bear rate. I am arguing both tails are thinner than the dc-infra node implies, because the node poo | high |
Management guides double-digit core FFO growth for multiple years (2026Q2) and reports +66.7% >1MW renewal spreads, while FY2025 FMP key-metrics show ROIC of 1.30% and ROE of 5.71%, and recurring capex plus capitalised l | high |
Customer capex evidence is overwhelming and FACT-graded at the customer — MSFT citing USD 368bn contracted backlog and ~USD 175bn CY2026 capex, GOOGL USD 514bn cloud backlog, AMZN backlog "substantially continuing to gro | high |
Price 200.15 versus a 52-week high of 208.14 — the market is pricing this name within 4% of its best level in a year, at 20.6x EV/EBITDA. My -25% bear takes it to ~150, which is the bottom of the same 52-week range. The | medium |
All four signal desks are unbuilt, so no cross-dimension check exists on this name. The conflict is with the SYSTEM design (§P3 expects disagreement across desks to be the output), not with a signal — I cannot report agr | medium |
| archived | hash | bytes |
|---|---|---|
| 2026-08-17T15:40:00 | 7330fbb73ca9 | 37,247 |