Get Free Teaser
Methodology and result · 26 October 2026

Reconciliation — India’s counted capacity, rebuiltGridvik registry · 242 source records · 130 counted · Operating 778.69 MW · Building 499.00 MW · Pipeline 2,236.00 MW

Document GRIDVIK-RECONMethod — four stated rules242 source records reconciled130 records countedReplaces 2,420.37 MW as a single figure
Operating tier verified at 778.69 MWEvery exclusion carries a written reason1,456 MW of it is facility power, not ITThe old headline included a 512 MW approval
778.7MW
Operating
499.0MW
Under construction
2,236.0MW
Pipeline
1,277.7MW
Operating + building
130
Records counted
45
Ceilings set aside

Every published Indian data-centre capacity number is a sum of unlike things. Gridvik’s own registry was no exception: 2,420.37 MW across 86 records, in which an operating 0.3 MW exchange building and a 512 MW incentive approval carried equal weight, and in which gross facility power was added to IT load. This document rebuilds that number from the 242 source records using four rules, each of which can be checked against the audit file published beside it. The result is not one figure. It is three: 778.69 MW operating, 499.00 MW under construction, and 2,236.00 MW announced, approved or unverified. The old headline was larger than the first two combined and smaller than the third. It described no single thing, which is why it could not survive a diligence call.

1At a glance

Source records
242 across 49 fields, master of 18 October 2026, revised 26 October 2026
Records counted after reconciliation
130
Operating
778.69 MW across 49 records
Operating, IT basis only
602.7 MW — the most defensible single number in the file
Under construction
499.00 MW across 13 records
Announced, approved or unverified
2,236.00 MW across 68 records
Operating plus building
1,277.69 MW
Previous headline
2,420.4 MW across 86 records, single undifferentiated sum
Net change to the total
+1,093.32 MW — explained line by line below
Container ceilings set aside
45 records, not counted
Unverified records set aside
36 records with an UNKNOWN flag, not counted
Largest operating operator
NTT Global Data Centers at 273.2 MW
Largest building programme
STT GDC India at 131.5 MW under construction
Audit trail
Record-level CSV published with this document

2One number, four different things

Pipelineannounced or unverified2,236.0 MWOld headlineone undifferentiated sum2,420.4 MWOperating + buildingthe defensible total1,277.7 MWUnder constructioncapital committed499.0 MWOperatingverified operating buildings778.7 MWThe old headline sat between two tiers and described neither. Red and blue are buildings; grey is a promise.
Figure 1 — the reconciled tiers against the old headline. The old figure sat above operating capacity and below the pipeline, and described neither.
What the old 2,420.37 MW actually contained
ComponentSizeWhat it was measuring
Operating buildingsabout 778.7 MWEnergised capacity in named facilities
Under constructionabout 499.0 MWCommitted capital, no revenue yet
Announced or plannedabout 700 MWIntentions with dates
Stage unverified601 MWFive AirTrunk facilities whose status the file could not confirm
A project approval512 MWAM AI Factory Vizag, approved and incentivised, construction unverified
Gross facility powerabout 106 MWCapitaLand towers counted at gross, not IT load
Unresolved basisabout 1,456 MWRecords whose published figure may be facility power rather than IT

Two records are enough to show why the old number could not be defended. PRJ-060, the AM AI Factory at Visakhapatnam, contributed 512 MW — 21% of the entire total — on an approved incentive application with unverified construction. And five AirTrunk facilities contributed 601 MW — another 25% — with a stage the source register itself records as unverified.

Put differently, 46% of the old headline came from records that are not operating buildings. That does not make them worthless. An approved 512 MW AI factory is one of the most important facts in the registry. It simply is not capacity, and adding it to a 0.3 MW telephone-exchange building produces a number that means nothing.

Why this matters commercially, not academically

A capacity total is the first thing an acquirer, a lender or a hyperscale site-selection team asks for. If the first number you give them does not survive one follow-up question, nothing else in the file gets read.

The old figure was not exaggerated in bad faith — it was a sum of every record someone had marked additive. The failure was the flag, not the motive.

What follows is the fix, and it is deliberately unflattering: the defensible number is roughly half the old headline.

3The four rules

Every decision in the audit file follows one of four rules. Each is stated so that a reader can disagree with it, and if they do, recalculate in minutes from the published CSV.

The rules, and the failure each one prevents
RuleWhat it doesFailure it prevents
1 — ScopeOne basis per record: IT load where the operator publishes it, otherwise the publisher’s own figure, flagged as facility basisAdding gross facility power to IT load, which inflates a total by 20 to 40%
2 — LevelCount the most granular record carrying capacity. A campus, city portfolio, programme, acquisition or tenant deployment is a container and is never countedThe same steel counted two or three times, or — the worse error — counted zero times
3 — StageEvery counted record lands in exactly one tier: operating, building, or pipelineAn approved application and an energised building carrying the same weight
4 — MacroMoUs, financing events, market references, network records and investment programmes are not capacity and are excludedA 2.8 GW utility opportunity pipeline appearing in a data-centre total

Rule 2 is the one that changed the most numbers, and it cut in both directions. It removed 72 MW from PDG Chennai, a campus claim with no building breakdown, and it added 171 MW of STT GDC Palava buildings that had previously been marked non-additive along with their parent campus — so the capacity had vanished from the total entirely.

That second case was a systematic error. Forty-five container records and their children were all flagged non-additive, which meant a campus could be recorded, described and dated in the file while contributing nothing to the sum. West Bengal was the clearest casualty: four operators, about 95 MW published, and 1.08 MW counted.

Why the containers are set aside rather than converted

A container is not wrong. A campus figure is often the only thing an operator publishes, and the STT Palava campus at 400 MW is a real statement about a real site.

But converting a container into building capacity requires inventing a building schedule. This registry does not invent. So the 45 container ceilings are reported separately, at their published figures, and excluded from every total on this page.

Their combined published value is 22,200.8 MW — which is the correct denominator for the question how much has India announced, and the wrong one for how much does India have.

4The reconciled ladder

The reconciled totals
TierRecordsMWWhat it counts
Operating49778.69Named buildings the source records as operational, live or expanding
— of which IT basis—602.7Operator-stated IT load, excluding facility power and unstated bases
Under construction13499.00Physically being built, capital committed, no revenue
Pipeline682,236.0Announced, planned, approved or stage-unverified
Operating plus building621,277.69The defensible number for capacity that exists or is being built
All counted records1303,513.69Every tier, for comparison with the old headline

The single most useful number in this registry is 778.69 MW — verified operating capacity across 49 named buildings. It is a floor, not a census: it counts only capacity that carries a building-level record, so a facility with no record of its own contributes nothing even if it is running.

602.69 MW of that 778.69 is on an IT-load basis and the rest is published facility power or an unstated basis. That split matters more than the total. A wholesale customer buys IT load; a utility sells facility power. Mixing them is how a 62 MW facility becomes a 62 MW IT claim.

The basis mix inside each tier
BasisMWWhat a reader should do with it
IT (operator-stated)1,441.9Comparable across operators; use for pricing per MW
IT (bare)7.2Scope states IT but no figure was restated
Facility or unresolved1,456.1Divide by a stated PUE before comparing with IT
Basis not stated608.5Old records; treat as IT until checked

1,456 MW of the reconciled total is facility power or an unresolved basis. Converting it to IT load requires a PUE assumption per record, and this file does not make one globally — the declared PUEs range from 1.40 to 1.70, so a blanket 1.5 would misstate individual buildings by up to 13%. The basis is flagged per record in the audit file instead.

5Where the 2,420.37 MW went

The bridge, line by line
StepMWExplanation
Previous headline2,420.486 records flagged additive
Removed: container converted to ceiling−72.0PDG CH1 Chennai campus at 72 MW had no building breakdown
Removed: gross power restated to IT−68.0Four CapitaLand towers, previously 200 MW, restated to 132 MW on an IT basis
Removed: IT rebase−1.0STT GDC Ahmedabad 1, 4 MW restated to 3 MW
Added: children of orphaned containers+1,234.3Records whose parent and self were both marked non-additive
Reconciled total3,513.69130 records across three tiers

The additions are the part that would never have been found by inspection. When a campus row and its building rows are all marked non-additive, nothing in any report looks wrong — the records are present, dated and sourced. They simply never enter a total.

What was recovered, by family
FamilyRecordsMWWhy it had been lost
STT GDC26486.7Campus and city-portfolio rows flagged non-additive; every building under them inherited the flag
NTT Global11261.6Mahape, Noida 2, Bengaluru 4 and Chennai 2 buildings under non-additive campuses
CtrlS6161.8Six Mumbai, Chennai, Delhi and Kolkata buildings with no additive parent
Princeton Digital2148.0MU1 expansion phase, child of a non-additive campus
Sify269.2Rabale Tower 5 and Siruseri, the estate’s two largest facilities
Nxtra322.0Three Chennai buildings under non-additive city records

Sify Rabale is the case worth remembering. It is the operator’s largest campus, a DGX-Ready certified campus by its own account, and it publishes 96.94 MW built across five towers. Under the previous method it contributed nothing to the national figure, because the campus row and the tower rows were all marked non-additive. The reconciliation recovers 43.3 MW — Tower 5 only, because the other four towers have no separate records. Even the corrected figure is a floor.

6Operators, ranked by operating capacity

NTTGlobal Data Centers273.2YottaData Services145.8SifyTechnologies125.1Princeton DigiPrinceton Digital Group48.0Nxtraby Airtel38.0AdaniEnterprises35.0STT GDCIndia35.0CapitaLandIndia Trust34.0CtrlSDatacenters33.1Ranked on verified operating capacity only. Pipeline is excluded from every bar.
Figure 2 — verified operating capacity by operator. This ranking is materially different from the one produced by adding up every additive record.
Operating, building and pipeline by operator
OperatorOperatingBuildingPipeline
NTT Global Data Centers273.2—169.4
Yotta Data Services145.8—120.0
Sify Technologies125.1—30.0
Princeton Digital Group48.0100.0—
Nxtra by Airtel38.0—238.2
Adani Enterprises35.0—6.0
STT GDC India35.0131.5329.2
CapitaLand India Trust34.061.037.0
CtrlS Datacenters33.112.0193.2

The largest operating data-centre operator in India, on this registry’s evidence, is NTT Global Data Centers at 273.2 MW. That is a correction to an earlier claim on the Yotta pages, which described Yotta as the largest additive operator at 236 MW — a figure produced by adding its 1 MW and 2 MW facilities to its 60 and 120 MW ones without separating stage.

On operating capacity the order is NTT 273.2, Yotta 145.8, Sify 125.1. On pipeline the order reverses: STT GDC 329.2 MW announced against 35.0 MW operating, and CtrlS 193.2 against 33.1. Those ratios are the most interesting numbers on this page.

Nxtra by Airtel is the other outlier: 38.0 MW operating against 238.2 MW in pipeline. Eighteen Nxtra facility records are marked stage-unverified in the source register, which is why they sit in the pipeline tier despite the facilities being real and in service. That is a data-quality limit of this file, not a market statement, and it is the largest single item in the review queue below.

7States, reconciled

States, by tier
StateOld figureOperatingBuildingPipelineTotal
Maharashtra786.4376.7355.0820.21,551.9
Uttar Pradesh331.1163.539.0248.4450.9
Tamil Nadu296.6115.966.0201.6383.5
Karnataka90.754.7—125.8180.5
Telangana341.319.927.0283.4330.3
West Bengal1.117.1—15.432.5
Bihar12.112.1——12.1
Madhya Pradesh12.0—12.0—12.0
Rajasthan6.06.0——6.0
Odisha6.85.0—1.86.8

Three states change character under reconciliation. Telangana’s 341.3 MW becomes 19.9 MW operating, because 283.4 MW of it is AirTrunk HYD1 and CtrlS Chandanvelly at unverified or planned stage. Andhra Pradesh’s 512.0 MW becomes 512.0 MW of pipeline and nothing operating. And Maharashtra’s 786.4 MW becomes 328.7 MW operating with 820.2 MW still to be built.

Those are not declines. They are the same facts described accurately. A state with 328.7 MW operating and 820.2 MW under construction or announced is a far more useful object than a state with “786.4 MW”.

This document does not change the 230 published record pages

The record pages quote state shares from the source register at the time each page was built — Maharashtra 786.4 MW, Tamil Nadu 296.6 MW, Uttar Pradesh 331.06 MW. Those figures remain the registry’s source-register view and are not silently overwritten.

The reconciled view on this page is published alongside, not on top. Two labelled numbers with a stated method are stronger in diligence than one number whose method is invisible.

If a single number is preferred, the switch is a site-wide regeneration and a re-verification of 230 pages. That work is scoped but not done.

8What is set aside

What is excluded from every total here
CategoryRecordsMWWhy excluded
Container ceilings, excluded4510,298.8Campus, portfolio and programme claims with no building breakdown
Container records declaring capacity, in total4422,200.8The honest denominator for “India has announced” claims
Of which 1 GW or larger1117,300.0Reliance Jamnagar 3 GW, AirTrunk Raigad 3 GW, Tata Power 2.8 GW, and eight 1 GW programmes
Unverified records (UNKNOWN)3611,152.0Additive status never established; includes Yotta West Bengal at 250 MW
Macro records——MoUs, financing, network, market references, investment programmes
Zero-capacity records50.0Live halls that publish no megawatt figure: Iron Mountain MUM-1, MUM-2 and NCR-1, Colt Mumbai 1 and 2

The 1 GW-scale records deserve a note because they are the most quoted numbers in Indian data-centre press. Eleven records in this file declare 1 GW or more, 17,300 MW between them — Reliance Jamnagar at 3 GW, AirTrunk Raigad at 3 GW, Tata Power’s 2.8 GW opportunity pipeline, Reliance Bhogapuram at 1.5 GW, and eight separate 1 GW programmes from Google, Adani, AdaniConneX, TCS, Digital Connexion and High Density Data Centre.

Setting them aside is not scepticism about the companies. It is the only way to keep the words “megawatts” and “buildings” in the same sentence. A reader who wants the announcement total has it: 22,200.8 MW of declared ceilings, which is the honest denominator for a media figure like “India has announced 20 GW”.

9What is still open, and what changes

This document fixes the structure. It does not fix the source data, and four things remain open.

The review queue
ItemSizeWhat would close it
Nxtra facilities marked stage-unverified21 records, 238.2 MWConfirm operating status per facility; would move up to 238 MW into the operating tier
AirTrunk facilities marked stage-unverified5 records, 601.0 MWThe single largest item in the pipeline tier; needs one commissioned-capacity statement
Facility-power records with no IT figure1,456.1 MWA per-facility IT load or a stated PUE
Records with no capacity at all6 operating facilitiesIron Mountain and Colt publish no megawatt figure for several live halls
Cross-record overlaps the parent graph missesabout 14 MW suspectedNxtra Chennai: PRJ-011 at 38 MW plus three CHE buildings at 22 MW, against a 46 MW city portfolio
Contracted power counted as facility powerPRJ-208, 64 MWColt Mumbai 3 publishes 64 MW of contracted power, not IT load; the largest single facility-basis item in the building tier
Container ceilings needing a building schedule45 recordsA per-building split, which for STT GDC and CtrlS is 15 records each

The Nxtra and AirTrunk items are worth more than everything else combined — 839 MW sitting in the pipeline tier for want of a status confirmation, against a 778.69 MW operating total. Confirming them would more than double the defensible figure. Not confirming them is why the operating number is a floor.

Three claims elsewhere in this registry are now known to be wrong and are corrected here:

Claims this reconciliation corrects
ClaimCorrect position
“Yotta is the largest additive operator at 236 MW”NTT is the largest by operating capacity at 273.2 MW; Yotta is second at 145.8 MW
“2,420.37 MW counted nationally”1,277.7 MW operating plus under construction, and 2,236.0 MW announced
“West Bengal has 1.08 MW; Delhi has 0 MW”A flag artefact, not a market fact. West Bengal publishes about 95 MW; the reconciliation recovers 17.1 MW operating and 15.4 MW pipeline
The one line to use in a room

India’s named data-centre estate: 778.69 MW operating, 499.00 MW under construction, 2,236.00 MW announced — from 130 building-level records.

Every figure is traceable to a row in the audit file, and every exclusion has a written reason. That is the difference between a number and a claim.

The conservative alternative, if only operator-stated IT load is acceptable: 602.7 MW operating.

10Sources and audit file

Sources: the Gridvik India data centre master of 18 October 2026, revised 26 October 2026, 242 records across 49 fields of which 241 are distinct facilities; the Gridvik source register of 133 sources with withheld URLs; and the record-level audit file published with this document, which lists every one of the 242 records with its basis, decision, reason and reconciled megawatts. Methodology dated 26 October 2026. Figures are re-derivable by any reader from the audit file.