Google New Albany: Central Ohio growth needs operator and campus separation
FJI source-qualified: four-document gate met, including project-specific government evidence. Qualification evidence and decisions →
Project status: Existing operator-listed Ohio location; current campus acceptance and load undisclosed. Capacity scope: Campus IT MW and current utilization undisclosed. How we verify evidence.
← Back to project indexCompare this project → · Track its catalysts → · Evidence guide →
- Location
- New Albany, Ohio — representative locality pin
- Readiness
- Existing facility / readiness unverified
- Status
- Existing operator-listed Ohio location; current campus acceptance and load undisclosed
- Confirmed companies
- Google / Alphabet
- Next milestone
- Campus-only capital allocation, useful load and resource-service readiness
- Reviewed
- October 6, 2026
Expanded analysis · Original disclosures linked below · CAD and USD preserved as labeled · Company statements attributed; interpretations labeled.
The one-minute investment takeaway
Our analysis: Central Ohio growth needs operator and campus separation. Google New Albany is a distinct project from the QTS location already covered. Its statewide scale should not be mistaken for site-level accepted computing or capital.
Readiness basis: Classification of evidence in the reviewed profile; strongest documented phase, not full-campus completion. Existing operator-listed Ohio location; current campus acceptance and load undisclosed Readiness source →
What the sources establish
- Distinct campus identity. Google’s Ohio page identifies New Albany alongside Lancaster and Columbus, and records New Albany construction beginning in 2019. This is distinct from QTS New Albany. Primary source →
- Portfolio scope. The page reports more than USD 20 billion invested in Ohio since 2019. This spans a multi-location program and is not New Albany’s site-only budget. Primary source →
Who receives the money?
Our analysis of disclosed roles. Revenue routes are business-model interpretations, not estimates of booked project revenue.
| Company / exposure | Economic role | What investors need to establish |
|---|---|---|
| Google / Alphabet | Owner or operator of the disclosed infrastructure | Accepted useful capacity and net contribution after resource and renewal costs. |
| Named service and construction participants | Contract-specific delivery and recurring service roles | Actual contract, tariff or purchase terms; participation is not booked profit. |
| Equipment suppliers not established here | Potential procurement and renewal spending | Named awarded orders before attributing public-company project revenue. |
How financially meaningful is it?
Our analysis: A regional cluster can share workforce and network capabilities while putting pressure on common electrical and construction resources. The investor model needs the actual campus’s delivered capital and accepted workloads, not a regional allocation chosen for convenience. Google’s Ohio footprint includes at least three identified locations; their investment and service milestones cannot be aggregated under New Albany. The nearby QTS site has a different owner and commercial model, even where representative map coordinates form a cluster. Google’s owner-user benefit arrives through cloud and product contribution rather than rent from itself. Underwrite equipment renewal, operating power and common infrastructure consistently across phases. An existing listing demonstrates the location’s role in the network, but current IT MW and campus-attributable financial results remain open diligence questions. Avoid treating regional cloud availability as a disclosure of a particular hall’s utilization.
Computing contribution equals customer or product benefit minus power, network, facility operation, financing and equipment renewal. Model long-lived buildings separately from shorter-lived computing assets.
Hypothetical illustration: 10 MW steady IT load at 1.2 PUE uses 105,120 MWh annually. A USD 10/MWh tariff increase adds USD 1.0512 million annual cost. Neither load, PUE nor tariff is disclosed here; this is a sensitivity example, not a site forecast.
Milestones that would change the assessment
| Milestone | Evidence to watch |
|---|---|
| Scope and capital | Reconcile campus and portfolio figures, accepted versus potential capacity, and property versus equipment funding. |
| Electrical and cooling acceptance | Campus-specific expansion scope, operating load and renewal productivity. Equipment delivery, construction completion and commissioning are separate steps. |
| Commercial productivity | Useful workloads or billable customer capacity, with operating costs and renewal obligations included. |
| Counterparty attribution | Named binding service and procurement terms before estimating participant earnings. |
What could break the investment case?
Our analysis: Common utility bottlenecks, costly density upgrades and regional capital misallocation can weaken apparent returns. Shared geography does not establish shared ownership or tenants.
What would change our view?
Our analysis: Dated acceptance, improved useful output and competitive net resource costs would strengthen our assessment. Underutilized capacity, expensive upgrades without customer support, or rising renewal costs ahead of economic benefits would weaken it. We would update this profile using campus-specific operating and contractual evidence. A larger corporate investment headline, a grant program or a design capability alone would not establish a stronger return.
What remains unknown
Current accepted IT MW, facility load, billable occupancy or workload utilization, site-attributable earnings, tariff details, phase capital, supplier contract values and measured performance remain unestablished unless explicitly stated above. Operator specifications are not independently measured outcomes. The pin represents the locality rather than a verified server hall. Broad portfolio AI demand is not proof of a dedicated AI deployment here.
Project research for information, not a buy recommendation. Financial illustrations use assumptions, not disclosed site results or management guidance.
Company investor information & quarterly statements
Alphabet
Project participant recorded in reviewed project profile; consolidated corporate disclosure only
Official investor & shareholder information · Quarterly financial statements: 2026 Q2, quarter ended June 30, 2026
Corporate disclosures provide company-wide context. They do not establish this project’s revenue, spending, profit, ownership share or operating capacity. Disclosure verification records →