Skip to content
Reality Check
Menu
Stage unconfirmed

Polarise Amberg AI Factory — Wertachtal

Former Wertachtal transmitter, Amberg, Unterallgäu, Bavaria, Germany

Reviewed 9 Oct 20266 sources
Watch this site

Watch Polarise Amberg AI Factory — Wertachtal

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.

Fields marked * are required.

Checking enquiry availability…

Request details

Register your interest in monitoring this record. Alerts are not active yet. Site Watch will cost €150 per site per month excluding VAT after any included trial.

Optional. Public information only. Do not include confidential or non-public information.

Project brief

Bounded, developer-led reuse proposal at the former Wertachtal transmitter. Public evidence supports a pre-planning concept and historical consortium control of the broader conversion area, but not a completed…

Read overview
Next check

Identify the DSO and exact connection node/voltage, then obtain the application, connection offer/agreement, staged firm/flexible import and energisation terms. Keep generation, BESS, equipment, historical…

Open the full check

Overview

Bounded, developer-led reuse proposal at the former Wertachtal transmitter. Public evidence supports a pre-planning concept and historical consortium control of the broader conversion area, but not a completed Polarise acquisition, exact parcel title, planning application, grid import right, physical fibre route or named customer. The 69.5/70 MWp solar park, planned wind and BESS are generation/storage context and do not establish continuous data-centre import. This is market intelligence, not off-market land.

Developer / applicant
Polarise
Owner
Stadtwerke Bad Vilbel and Bürgerstiftung Bad Vilbel (historical conversion-area consortium and proposed seller; exact current data-centre parcel title and transfer unverified)
Operator
Polarise (intended)

Planning and delivery status

Pre-planning, not a submitted or permitted data centre. On 13 March 2026 the mayor described only an oral request and said implementation/urban-development agreements must precede a land-use-plan amendment and project-specific development plan. The current municipal planning page does not list a Wertachtal data-centre procedure. Mid-2027 remains a promoter target, not a permission, construction start or energisation date.

Stage source: 13 Mar 2026

Project 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 levels
01

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?
Event date
Unknown

Not established from the public records reviewed.

What is the effective date of the applied connection evidence?
Capacity boundary
Unknown

Not established from the public records reviewed.

Which buildings or phases does the applied connection evidence cover?
Verification
Unknown
02

Offered

Unknown

Not established from the public records reviewed.

What offered mva is evidenced for the assessed site scope?
Event date
Unknown

Not established from the public records reviewed.

What is the effective date of the offered connection evidence?
Capacity boundary
Unknown

Not established from the public records reviewed.

Which buildings or phases does the offered connection evidence cover?
Verification
Unknown
03

Accepted / contracted

Unknown

Not established from the public records reviewed.

What accepted or contracted mva is evidenced for the assessed site scope?
Event date
Unknown

Not established from the public records reviewed.

What is the effective date of the accepted connection evidence?
Capacity boundary
Unknown

Not established from the public records reviewed.

Which buildings or phases does the accepted connection evidence cover?
Verification
Unknown
04

Energised

Unknown

Not established from the public records reviewed.

What energised mva is evidenced for the assessed site scope?
Event date
Unknown

Not established from the public records reviewed.

What is the effective date of the energised connection evidence?
Capacity boundary
Unknown

Not established from the public records reviewed.

Which buildings or phases does the energised connection evidence cover?
Verification
Unknown
Connection point and load boundaries
Network operator
Unknown

Not established from the public records reviewed.

Which TSO or DSO is responsible for this demand connection?
Connection point
Unknown

Not established from the public records reviewed.

What is the operator-confirmed connection substation or circuit?
Voltage
Unknown

Not established from the public records reviewed.

What voltage level is specified for the demand connection?
Straight-line distance
Unknown

Not established from the public records reviewed.

What are the evidenced site and connection-point coordinates, and their calculated straight-line distance?
Published route length
Unknown

Not established from the public records reviewed.

What grid route length is published, and for which circuit?

IT load

Unknown

Not established from the public records reviewed.

What is the published IT load in MW?
Basis
Unknown

Not established from the public records reviewed.

On what electrical basis is the IT load in MW stated?
Site / phase boundary
Unknown

Not established from the public records reviewed.

Which phase or campus does the IT load in MW cover?

Facility load

Unknown

Not established from the public records reviewed.

What is the published facility load in MW?
Basis
Unknown

Not established from the public records reviewed.

On what electrical basis is the facility load in MW stated?
Site / phase boundary
Unknown

Not established from the public records reviewed.

Which phase or campus does the facility load in MW cover?

Import capacity

Unknown

Not established from the public records reviewed.

What is the published import capacity in MVA?
Basis
Unknown

Not established from the public records reviewed.

On what electrical basis is the import capacity in MVA stated?
Site / phase boundary
Unknown

Not established from the public records reviewed.

Which phase or campus does the import capacity in MVA cover?

These are different electrical quantities. No power factor, PUE or available import is assumed from an IT-load statement.

Connection agreement and conditions
Agreement type
Unknown

Not established from the public records reviewed.

What connection agreement type and current status are documented?
Phased capacity
Unknown

Not established from the public records reviewed.

Does the agreement impose phased import-capacity limits?
Flexibility obligations
Unknown

Not established from the public records reviewed.

What flexibility or curtailment obligations apply?
On-site generation obligations
Unknown

Not established from the public records reviewed.

What on-site generation obligations apply?
Securities posted
Unknown

Not established from the public records reviewed.

What securities are required, posted and still valid?
Longstop dates
Unknown

Not established from the public records reviewed.

What connection longstop or milestone dates apply?
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.

Published connection works scope
Unknown

Not established from the public records reviewed.

What complete connection scope is published: bays, stations, voltage, circuits, route lengths and underground or overhead configuration?
Scope completeness
Unknown

Not established from the public records reviewed.

Is the published connection scope complete enough to match every component to a sourced benchmark?

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
  1. Which TSO or DSO is responsible for this demand connection?

    Not established from the public records reviewed.

  2. What is the operator-confirmed connection substation or circuit?

    Not established from the public records reviewed.

  3. What voltage level is specified for the demand connection?

    Not established from the public records reviewed.

  4. What are the evidenced site and connection-point coordinates, and their calculated straight-line distance?

    Not established from the public records reviewed.

  5. What grid route length is published, and for which circuit?

    Not established from the public records reviewed.

  6. What applied mva is evidenced for the assessed site scope?

    Not established from the public records reviewed.

  7. What is the effective date of the applied connection evidence?

    Not established from the public records reviewed.

  8. Which buildings or phases does the applied connection evidence cover?

    Not established from the public records reviewed.

  9. What evidence level can be supported for capacityLadder.applied?

    Verification has not been established.

  10. What offered mva is evidenced for the assessed site scope?

    Not established from the public records reviewed.

  11. What is the effective date of the offered connection evidence?

    Not established from the public records reviewed.

  12. Which buildings or phases does the offered connection evidence cover?

    Not established from the public records reviewed.

  13. What evidence level can be supported for capacityLadder.offered?

    Verification has not been established.

  14. What accepted or contracted mva is evidenced for the assessed site scope?

    Not established from the public records reviewed.

  15. What is the effective date of the accepted connection evidence?

    Not established from the public records reviewed.

  16. Which buildings or phases does the accepted connection evidence cover?

    Not established from the public records reviewed.

  17. What evidence level can be supported for capacityLadder.accepted?

    Verification has not been established.

  18. What energised mva is evidenced for the assessed site scope?

    Not established from the public records reviewed.

  19. What is the effective date of the energised connection evidence?

    Not established from the public records reviewed.

  20. Which buildings or phases does the energised connection evidence cover?

    Not established from the public records reviewed.

  21. What evidence level can be supported for capacityLadder.energised?

    Verification has not been established.

  22. What connection agreement type and current status are documented?

    Not established from the public records reviewed.

  23. Does the agreement impose phased import-capacity limits?

    Not established from the public records reviewed.

  24. What flexibility or curtailment obligations apply?

    Not established from the public records reviewed.

  25. What on-site generation obligations apply?

    Not established from the public records reviewed.

  26. What securities are required, posted and still valid?

    Not established from the public records reviewed.

  27. What connection longstop or milestone dates apply?

    Not established from the public records reviewed.

  28. What is the published IT load in MW?

    Not established from the public records reviewed.

  29. On what electrical basis is the IT load in MW stated?

    Not established from the public records reviewed.

  30. Which phase or campus does the IT load in MW cover?

    Not established from the public records reviewed.

  31. What is the published facility load in MW?

    Not established from the public records reviewed.

  32. On what electrical basis is the facility load in MW stated?

    Not established from the public records reviewed.

  33. Which phase or campus does the facility load in MW cover?

    Not established from the public records reviewed.

  34. What is the published import capacity in MVA?

    Not established from the public records reviewed.

  35. On what electrical basis is the import capacity in MVA stated?

    Not established from the public records reviewed.

  36. Which phase or campus does the import capacity in MVA cover?

    Not established from the public records reviewed.

  37. 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.

  38. Which reinforcements does the connection depend on, and what dates are published?

    Not established from the public records reviewed.

  39. Which grid works require planning, and what is their current consent status and dated programme?

    Not established from the public records reviewed.

  40. Which connection-policy conditions apply, and when could they be satisfied?

    Not established from the public records reviewed.

  41. What complete connection scope is published: bays, stations, voltage, circuits, route lengths and underground or overhead configuration?

    Not established from the public records reviewed.

  42. Is the published connection scope complete enough to match every component to a sourced benchmark?

    Not established from the public records reviewed.

  43. What behind-the-meter generation is evidenced, and at what scope?

    Not established from the public records reviewed.

  44. Does the applicable planning or connection policy require behind-the-meter generation?

    Not established from the public records reviewed.

  45. What battery storage is evidenced, and at what scope?

    Not established from the public records reviewed.

  46. Does the applicable planning or connection policy require battery storage?

    Not established from the public records reviewed.

  47. What a private wire is evidenced, and at what scope?

    Not established from the public records reviewed.

  48. Does the applicable planning or connection policy require a private wire?

    Not established from the public records reviewed.

  49. What gas supply or generation is evidenced, and at what scope?

    Not established from the public records reviewed.

  50. Does the applicable planning or connection policy require gas supply or generation?

    Not established from the public records reviewed.

  51. Does the published connection claim meet the policy applicable to its application date, location and agreement status?

    Not established from the public records reviewed.

  52. Which checked country-grid sources and location-specific constraints apply to this connection?

    No country-context relationship has been established for this record.

  53. Identify network and customer works, upstream reinforcement, land and wayleaves, taxes, fees, securities, contingency and the price base.

    Connection-cost scope question.

  54. Resolve the energisation input: A dated, document-verified import-MVA rung for the assessed scope.

    This missing input leaves an energisation bound unknown.

  55. 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.

  56. Resolve the energisation input: Connection-dependent reinforcement scope and completion dates

    This missing input leaves an energisation bound unknown.

  57. Resolve the energisation input: Grid-works planning status and programme

    This missing input leaves an energisation bound unknown.

  58. Resolve the energisation input: Applicable connection-policy conditions and programme

    This missing input leaves an energisation bound unknown.

  59. Obtain a published complete connection scope with voltage, configuration and measured quantities.

    This scope or reference gap prevents a complete indicative connection capex band.

  60. 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 Check
Earlier capacity notes and source context
65 MW unspecifiedProject capacity

Polarise's updated initial campus plan announced on 18 August 2026. It is not verified IT load, utility import entitlement or commissioned capacity.

Published claimCapacity source
30 MW unspecifiedOriginal initial plan (superseded)

Original 10 March 2026 promoter plan, superseded by the later 65 MW initial plan; not import or operating IT load.

Published claimCapacity source
120 MW unspecifiedUltimate scalable plan

Promoter's potential ultimate scale inclusive of the initial phase; not additional capacity or secured import.

Published claimCapacity source
Import rights and connection evidence

Polarise's current initial 65 MW and ultimate 120 MW figures have unspecified electrical scope. The 69.5/70 MWp existing solar park, proposed additional photovoltaic capacity, planned wind, BESS and CHP are generation/storage context only. No site-specific DSO connection offer, import right, node, voltage, route or firm/flexible terms were found in this review.

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

5 of 10 categories contain evidence. Each status applies to its specific claim.

Planning & decisions

Partial evidence

The mayor reported an oral request on 13 March 2026 and said implementation/urban-development agreements must precede a land-use-plan amendment and project-specific development plan. No Wertachtal data-centre procedure appears on the municipality's current published planning page; this does not prove that no unpublished or later step exists.

Sources & next check
Evidence reviewed 9 Oct 2026

Next check

Obtain executed agreements, council plan-initiation resolutions, the land-use-plan amendment and project development plan, environmental/noise files, formal application and decision.

Grid & import rights

Unverified

Polarise's current initial 65 MW and ultimate 120 MW figures have unspecified electrical scope. The 69.5/70 MWp existing solar park, proposed additional photovoltaic capacity, planned wind, BESS and CHP are generation/storage context only. No site-specific DSO connection offer, import right, node, voltage, route or firm/flexible terms were found in this review.

Sources & next check
Evidence reviewed 9 Oct 2026

Next check

Identify the DSO and exact connection node/voltage, then obtain the application, connection offer/agreement, staged firm/flexible import and energisation terms. Keep generation, BESS, equipment, historical demand and import scopes separate.

Ownership & development control

Partial evidence

Stadtwerke Bad Vilbel records a joint 2017 acquisition of the broader Wertachtal conversion area with Bürgerstiftung Bad Vilbel. Its 2026/27 business plan describes the site and sales of land not needed for the energy project. Polarise says it plans to acquire the former transmitter building and adjacent land; closing and exact parcel title have not been verified.

Sources & next check
Evidence reviewed 9 Oct 2026

Next check

Retrieve the cadastral redline, registered title and encumbrances, seller resolutions and evidence of the Polarise transfer closing; do not infer third-party availability.

Demand & location fit

Partial evidence

Polarise is the named intended AI-cloud operator/developer, and its platform financing announcement cites sovereign-AI demand. No named Amberg customer, signed site allocation, GPU deployment or leased load is public.

Sources & next check
Evidence reviewed 9 Oct 2026

Next check

Verify a site-specific customer or allocation, contracted compute delivery and phase mapping; do not infer Amberg demand from Polarise's platform pipeline or financing.

Programme & delivery

Partial evidence

Polarise targets mid-2027 and has announced platform debt financing up to an undisclosed substantial double-digit euro amount. Neither establishes project finance, land closing, permission, construction, energisation or commissioning, and the authority evidence still shows pre-planning.

Sources & next check
Evidence reviewed 9 Oct 2026

Next check

Verify land closing, plan initiation, permission, phase-specific financing, contractor appointments, construction start and separate building/electrical handovers.

Not assessed

Land-use zoningFibre & dark fibreLand, footprint & accessFlood, ground & environmentWater, cooling & heat
Evidence still needed
  • Land-use zoning

    The site boundary has not been matched to the current adopted zoning map and data-centre use policy.

  • Fibre & dark fibre

    No verified site entry, dark-fibre offer or physically diverse route assessment is recorded. Regional coverage alone is insufficient.

  • Land, footprint & access

    Gross and net developable area, boundaries, access rights, easements, setbacks and expansion space need site-specific evidence.

  • Flood, ground & environment

    Flood risk, ground conditions, contamination, ecology, heritage, noise and air-quality constraints have not been fully assessed here.

  • Water, cooling & heat

    Water availability and discharge, cooling technology, peak demand, heat reuse and utility agreements remain to be verified.

Project team

Appointments are limited to the project, phase and scope supported by each source.

Specialists & vendors

WV EnergieOther projects

Energy and site partner named by Polarise for the pre-planning concept; not a campus-wide MEP, utility or construction appointment.

Appointment source

Unlisted roles have no project-specific appointment recorded.

Sources

Publication dates are shown where known. Review dates do not establish approval or commissioning.

  1. Polarise: Amberg proposal and planned acquisitionpolarise.eu · 10 Mar 2026
  2. Polarise: financing and updated 65 MW initial planpolarise.eu · 18 Aug 2026
  3. Gemeinde Amberg: current published land-use planning proceduresgemeinde-amberg.de · Publication date unstated
  4. Kreisbote: mayor describes oral request and required planning sequencekreisbote.de · 13 Mar 2026
  5. Stadtwerke Bad Vilbel: Wertachtal conversion-area acquisition chronologysw-bv.de · Publication date unstated
  6. Stadtwerke Bad Vilbel: 2026/27 business plan — Wertachtal land and generationrim.ekom21.de · 3 Nov 2025

Original documents and maps retain their rights. Public access does not grant commercial redistribution rights.