Operating GoWest data centre. Current operator claim is 9 MW IT; SMV published 8.2 MW IT at design stage. Lupp, SMV and ROM have distinct delivery appointments. The surrounding GoWest plan IX-55-3 was adopted…
Read overviewmaincubes BER01 — Go West campus
Berlin, Germany
Watch this site
Watch maincubes BER01 — Go West campus
Register interest in updates to planning status, grid position, capacity claims, delivery teams and policy exposure. Every Power Reality Check client receives 60 days of Site Watch on their assessed site when monitoring is available.
8 cited sources · 6 utility and planning categories reviewed.
Review evidence and gapsObtain BER01’s connection agreement and energised import limit; reconcile the regional reinforcement programme and historical/current IT figures.
Open the full checkOverview
Operating GoWest data centre. Current operator claim is 9 MW IT; SMV published 8.2 MW IT at design stage. Lupp, SMV and ROM have distinct delivery appointments. The surrounding GoWest plan IX-55-3 was adopted in 2026; utility import rights and building-specific permit conditions remain unverified.
- Developer / applicant
- maincubes
- Owner
- Not verified
- Operator
- maincubes
Planning and delivery status
Current operator facility page describes an operating facility; publication date unstated. Reviewed 26 September 2026.
Stage source: Publication date unstatedProject intelligence. This record does not establish that the land or facility is available to acquire.
POWER STUDY
Power
What the power evidence establishes
The site-specific connection scope has not been established for this record.
Power classDNo qualifying rung
No same-scope, dated import-MVA rung has document-seen or better verification. Nearby infrastructure, IT MW and marketing claims cannot upgrade the class.
The class describes published documentary evidence at its stated date. It does not prove current contractual rights, transferability or an energisation date.
Class describes evidence maturity. Public records do not prove current contractual rights, transferable capacity or an energisation date. This record has not received a complete power study review.
Read the rules and verification levels01
Capacity ladder and evidence
Each rung is a separate MVA claim for its stated site or phase. A missing rung is unknown.
01
Applied
Unknown
Not established from the public records reviewed.
What applied mva is evidenced for the assessed site scope?02
Offered
Unknown
Not established from the public records reviewed.
What offered mva is evidenced for the assessed site scope?03
Accepted / contracted
Unknown
Not established from the public records reviewed.
What accepted or contracted mva is evidenced for the assessed site scope?04
Energised
Unknown
Not established from the public records reviewed.
What energised mva is evidenced for the assessed site scope?02
Conflicts and scope comparisons
No conflicting pair is recorded. This does not establish that all public statements have been reconciled.
03
Germany grid context
Network publications frame the claim. They do not allocate capacity to this site.
No country context entries have been linked to this site. Applicable policy, capacity information and reinforcement dependencies need review.
04
Derived energisation window
Earliest plausible yearUnknown
Latest plausible yearUnknown
The observed inputs do not establish a bounded delivery range. Open bounds stay unknown.
Rule
Use only a same-scope, dated, document-verified capacity rung and an applicable duration to energisation published by the observed site operator. The named process operator and a named source publisher must match that operator. Earliest year is the maximum of stage date plus minimum duration and each evidenced readiness constraint. Latest year is the maximum of stage date plus maximum duration and each published upper constraint only when every required input is bounded. An offer-processing duration is excluded. A missing required input leaves the affected bound unknown; no padding or contractual delivery promise is inferred.
No observed inputs establish this result.
Dependencies driving the range
- Connection-dependent reinforcement scope and completion dates: unknown.
- Grid-works planning status and programme: unknown.
- Applicable connection-policy conditions and programme: unknown.
What the earliest case requires
- Connection-dependent reinforcement scope and completion dates introduces no later constraint than the earliest case; this remains unverified.
- Grid-works planning status and programme introduces no later constraint than the earliest case; this remains unverified.
- Applicable connection-policy conditions and programme introduces no later constraint than the earliest case; this remains unverified.
Missing inputs leave the range open
- A dated, document-verified import-MVA rung for the assessed scope.
- An applicable duration from the evidenced stage to energisation, published by and matched to the observed site operator, rather than an offer-processing target.
- Connection-dependent reinforcement scope and completion dates
- Grid-works planning status and programme
- Applicable connection-policy conditions and programme
05
Indicative HV and connection capex
Unknown
Rule and scope
Sum each published complete scope quantity multiplied by the matching published benchmark minimum and maximum. Configuration, voltage, route type, unit, country applicability, currency and explicit price base year must match. No assumed route length, transformer count, exchange rate, inflation, fee uplift or partial index is inserted. The result is an indicative benchmark band, not an operator quotation or contractual connection charge.
No observed inputs establish this result.
Scope questions
- Obtain a published complete connection scope with voltage, configuration and measured quantities.
- Establish that every necessary connection-work component is included in the published scope.
- Identify network and customer works, upstream reinforcement, land and wayleaves, taxes, fees, securities, contingency and the price base.
06
Alternatives and policy exposure
Behind-the-meter generation
Unknown
Not established from the public records reviewed.
What behind-the-meter generation is evidenced, and at what scope?Planning / policy requirement
Unknown
Not established from the public records reviewed.
Does the applicable planning or connection policy require behind-the-meter generation?Battery storage
Unknown
Not established from the public records reviewed.
What battery storage is evidenced, and at what scope?Planning / policy requirement
Unknown
Not established from the public records reviewed.
Does the applicable planning or connection policy require battery storage?Private wire
Unknown
Not established from the public records reviewed.
What a private wire is evidenced, and at what scope?Planning / policy requirement
Unknown
Not established from the public records reviewed.
Does the applicable planning or connection policy require a private wire?Gas
Unknown
Not established from the public records reviewed.
What gas supply or generation is evidenced, and at what scope?Planning / policy requirement
Unknown
Not established from the public records reviewed.
Does the applicable planning or connection policy require gas supply or generation?Connection claim against current policy
Unknown
Not established from the public records reviewed.
Does the published connection claim meet the policy applicable to its application date, location and agreement status?07
Open questions for a Reality Check
Generated from unknown fields, missing derivation inputs and unresolved evidence. The questions identify the documents or specialist checks needed next.
60 questions to resolve
- Which TSO or DSO is responsible for this demand connection?
Not established from the public records reviewed.
- What is the operator-confirmed connection substation or circuit?
Not established from the public records reviewed.
- What voltage level is specified for the demand connection?
Not established from the public records reviewed.
- What are the evidenced site and connection-point coordinates, and their calculated straight-line distance?
Not established from the public records reviewed.
- What grid route length is published, and for which circuit?
Not established from the public records reviewed.
- What applied mva is evidenced for the assessed site scope?
Not established from the public records reviewed.
- What is the effective date of the applied connection evidence?
Not established from the public records reviewed.
- Which buildings or phases does the applied connection evidence cover?
Not established from the public records reviewed.
- What evidence level can be supported for capacityLadder.applied?
Verification has not been established.
- What offered mva is evidenced for the assessed site scope?
Not established from the public records reviewed.
- What is the effective date of the offered connection evidence?
Not established from the public records reviewed.
- Which buildings or phases does the offered connection evidence cover?
Not established from the public records reviewed.
- What evidence level can be supported for capacityLadder.offered?
Verification has not been established.
- What accepted or contracted mva is evidenced for the assessed site scope?
Not established from the public records reviewed.
- What is the effective date of the accepted connection evidence?
Not established from the public records reviewed.
- Which buildings or phases does the accepted connection evidence cover?
Not established from the public records reviewed.
- What evidence level can be supported for capacityLadder.accepted?
Verification has not been established.
- What energised mva is evidenced for the assessed site scope?
Not established from the public records reviewed.
- What is the effective date of the energised connection evidence?
Not established from the public records reviewed.
- Which buildings or phases does the energised connection evidence cover?
Not established from the public records reviewed.
- What evidence level can be supported for capacityLadder.energised?
Verification has not been established.
- What connection agreement type and current status are documented?
Not established from the public records reviewed.
- Does the agreement impose phased import-capacity limits?
Not established from the public records reviewed.
- What flexibility or curtailment obligations apply?
Not established from the public records reviewed.
- What on-site generation obligations apply?
Not established from the public records reviewed.
- What securities are required, posted and still valid?
Not established from the public records reviewed.
- What connection longstop or milestone dates apply?
Not established from the public records reviewed.
- What is the published IT load in MW?
Not established from the public records reviewed.
- On what electrical basis is the IT load in MW stated?
Not established from the public records reviewed.
- Which phase or campus does the IT load in MW cover?
Not established from the public records reviewed.
- What is the published facility load in MW?
Not established from the public records reviewed.
- On what electrical basis is the facility load in MW stated?
Not established from the public records reviewed.
- Which phase or campus does the facility load in MW cover?
Not established from the public records reviewed.
- What is the published import capacity in MVA?
Not established from the public records reviewed.
- On what electrical basis is the import capacity in MVA stated?
Not established from the public records reviewed.
- Which phase or campus does the import capacity in MVA cover?
Not established from the public records reviewed.
- What operator-published connection-to-energisation duration applies to this site and connection stage?
An application-to-offer processing target is not an energisation duration.
- Which reinforcements does the connection depend on, and what dates are published?
Not established from the public records reviewed.
- Which grid works require planning, and what is their current consent status and dated programme?
Not established from the public records reviewed.
- Which connection-policy conditions apply, and when could they be satisfied?
Not established from the public records reviewed.
- What complete connection scope is published: bays, stations, voltage, circuits, route lengths and underground or overhead configuration?
Not established from the public records reviewed.
- Is the published connection scope complete enough to match every component to a sourced benchmark?
Not established from the public records reviewed.
- What behind-the-meter generation is evidenced, and at what scope?
Not established from the public records reviewed.
- Does the applicable planning or connection policy require behind-the-meter generation?
Not established from the public records reviewed.
- What battery storage is evidenced, and at what scope?
Not established from the public records reviewed.
- Does the applicable planning or connection policy require battery storage?
Not established from the public records reviewed.
- What a private wire is evidenced, and at what scope?
Not established from the public records reviewed.
- Does the applicable planning or connection policy require a private wire?
Not established from the public records reviewed.
- What gas supply or generation is evidenced, and at what scope?
Not established from the public records reviewed.
- Does the applicable planning or connection policy require gas supply or generation?
Not established from the public records reviewed.
- Does the published connection claim meet the policy applicable to its application date, location and agreement status?
Not established from the public records reviewed.
- Which checked country-grid sources and location-specific constraints apply to this connection?
No country-context relationship has been established for this record.
- Identify network and customer works, upstream reinforcement, land and wayleaves, taxes, fees, securities, contingency and the price base.
Connection-cost scope question.
- Resolve the energisation input: A dated, document-verified import-MVA rung for the assessed scope.
This missing input leaves an energisation bound unknown.
- Resolve the energisation input: An applicable duration from the evidenced stage to energisation, published by and matched to the observed site operator, rather than an offer-processing target.
This missing input leaves an energisation bound unknown.
- Resolve the energisation input: Connection-dependent reinforcement scope and completion dates
This missing input leaves an energisation bound unknown.
- Resolve the energisation input: Grid-works planning status and programme
This missing input leaves an energisation bound unknown.
- Resolve the energisation input: Applicable connection-policy conditions and programme
This missing input leaves an energisation bound unknown.
- Obtain a published complete connection scope with voltage, configuration and measured quantities.
This scope or reference gap prevents a complete indicative connection capex band.
- Establish that every necessary connection-work component is included in the published scope.
This scope or reference gap prevents a complete indicative connection capex band.
Use these questions to scope a Power Reality Check.
Request an assessment of this record and the evidence needed next. Share only public information or documents you are authorised to provide.
Request a Reality CheckEarlier capacity notes and source context
9 MW ITProject capacity
BER01 facility, current operator claim; not utility import entitlement. Earlier design source stated 8.2 MW IT.
Published claimCapacity source8.2 MW ITEarlier design claim
BER01 design reported by project manager in November 2023; current operator page states 9 MW IT. Reconciliation of the design change is not published.
Published claimCapacity sourceImport rights and connection evidence
Current operator page states 9 MW IT and rotary UPS in an IP-bus configuration. SMV’s November 2023 design source states 8.2 MW IT. Neither establishes contracted import MW/MVA or spare connection rights. The 2026 planning justification records Stromnetz Berlin’s need to replace the Forckenbeckstraße substation for rising regional demand; it gives no BER01 allocation or spare import rights.
IT load, facility demand, import capacity and equipment ratings retain their stated scope. A published figure does not establish spare or transferable supply.
Planning & utilities
6 of 10 categories contain evidence. Each status applies to its specific claim.
Land-use zoning
Partial evidenceBerlin’s 28 April 2026 ordinance adopts the 13 November 2025 IX-55-3 plan for GoWest; publication on 8 May makes commencement 9 May 2026 under §5. The 2026 adoption bundle supplies the map and justification. BER01’s parcel-to-use/height/noise allocation remains unverified; adoption alone is not its building permit.
Sources & next check
Grid & import rights
Partial evidenceCurrent operator page states 9 MW IT and rotary UPS in an IP-bus configuration. SMV’s November 2023 design source states 8.2 MW IT. Neither establishes contracted import MW/MVA or spare connection rights. The 2026 planning justification records Stromnetz Berlin’s need to replace the Forckenbeckstraße substation for rising regional demand; it gives no BER01 allocation or spare import rights.
Sources & next check
Land, footprint & access
Partial evidenceLupp gives BER01 approximately 19,800 m² gross floor area across four full storeys and a basement. This building area is distinct from the operator’s 5,100 m² IT area and does not establish plot size or expansion land.
Sources & next check
Flood, ground & environment
Partial evidenceOperator reports independent EU Taxonomy assessment. The February 2026 GoWest justification identifies suspected-contamination register entry 18000 and contractual soil investigation/remediation duties. Further groundwater LHKW investigation was found unnecessary after sampling; this is not blanket remediation discharge or a BER01-specific compliance certificate.
Sources & next check
Water, cooling & heat
Partial evidenceOperator reports adiabatic cooling, room-specific air/water/immersion options and waste heat supplied directly to the adjacent GoWest district. The heat connection is reported by the operator; contracted offtake and water demand are not disclosed. The authority justification says nearby water/sewer connections remain subject to capacity and demand checks; the Mecklenburgische Straße trunk main is unavailable for direct connections.
Sources & next check
Programme & delivery
DocumentedSMV records construction starting in June 2023 and identifies Lupp’s structural/fit-out/envelope works, ROM’s technical-equipment package and SMV’s own project-management appointment. Current operator page states in operation.
Sources & next check
Not assessed
Planning & decisionsFibre & dark fibreOwnership & development controlDemand & location fit
Evidence still needed
- Planning & decisions
A current planning decision, conditions and any appeal or court proceedings still need to be checked.
- Fibre & dark fibre
No verified site entry, dark-fibre offer or physically diverse route assessment is recorded. Regional coverage alone is insufficient.
- Ownership & development control
Legal title, land-owning entity, development-control route and restrictions need verification. A named developer does not establish availability.
- Demand & location fit
Customer geography, latency, cloud or exchange nodes and a supported use case need project-specific evidence; national growth alone is insufficient.
Project team
Appointments are limited to the project, phase and scope supported by each source.
Main contractor
Adolf Lupp GmbH + Co. KGOther projects
BER01 extended shell contract. SMV identifies shell, fit-out, external works and façade packages; this does not establish responsibility for all MEP works.
Appointment sourceProject manager
SMV BauprojektsteuerungOther projects
BER01 project management for maincubes, confirmed by the project manager in November 2023.
Appointment sourceSpecialists & vendors
BER01 technical building equipment package, identified by SMV. Exact contracting legal entity and detailed MEP disciplines are not specified.
Appointment sourceUnlisted roles have no project-specific appointment recorded.
Sources
Publication dates are shown where known. Review dates do not establish approval or commissioning.
- maincubes BER01 — current facility specificationmaincubes.com · Publication date unstated
- maincubes confirms EU Taxonomy alignment for BER01maincubes.com · 9 Feb 2026
- Lupp — BER01 extended shell contractlupp.de · 27 Dec 2023
- SMV — BER01 project management and construction packagessmv.com · 29 Nov 2023
- Berlin Gazette — ordinance adopting GoWest plan IX-55-3, page 181berlin.de · 8 May 2026
- Charlottenburg-Wilmersdorf — IX-55-3 adoption procedure and plan annexesberlin.de · 10 Mar 2026
- Charlottenburg-Wilmersdorf — IX-55-3 plan of 13 November 2025, 10 March 2026 adoption bundleberlin.de · 10 Mar 2026
- Charlottenburg-Wilmersdorf — February 2026 IX-55-3 adoption justification, 10 March 2026 decision bundleberlin.de · 10 Mar 2026
Original documents and maps retain their rights. Public access does not grant commercial redistribution rights.