Locations in Sweden

Keep the objects separate

Luleå municipality sits in Norrbotten county and in SE1. Staffanstorp sits in Skåne and SE4. Gävle and Sandviken sit in SE2. Falun sits in Dalarna and SE3. Those facts answer different questions: who plans the land, which wholesale-price area applies, and which project rows are actually documented. A county slogan about hydropower does not replace a municipal detaljplan or a network-owner letter.

Stockholm County is the densest published colocation cluster in this register — Kista, Akalla, inner-city halls and Arlandastad development. Connectivity richness is documented on operator pages. Residual grid capacity is not inferred from that cluster. Districts inside one municipality are not interchangeable for fiber or power. A pin at municipality accuracy is weaker than a district pin, and both are weaker than a surveyed outline that this launch set does not publish.

What a missing file means

If a Swedish municipality does not appear here, DataCenterSweden has no finished file. That is not a finding that land, power or politics are absent. It is a coverage rule: empty county and municipality pages are not generated in order to look complete. Start from the reviewed geographies, then from the power and build guides, then from the official pages at the municipality, the network owner and Energimarknadsinspektionen.

A published geography is a reviewed file, not a name swap

The Locations hub lists geographies only when DataCenterSweden has a file worth reading. That file needs a defined geographic object, a short analysis, at least one related project or official hook and dated sources. A municipality name that can be inserted into a template is not enough. Do not generate empty county or municipality pages to create the appearance of national coverage.

The file should state its boundary and its last check. A county profile is not a municipality profile. A municipality profile is not a promise about every site inside its boundary. If a project is only named by an operator without a local planning or property source, describe the operator fact at that level. If the geography has no finished analysis, link the broader hub and say that the file is not yet published.

This rule helps the reader interpret absence correctly. A missing page means a missing reviewed publication, not a negative finding about land, power, politics or local interest. The register should never imply that a municipality is unsuitable merely because the editorial file has not been completed.

• Geographic kind and boundary.
• Dated summary and relevant questions.
• At least one related project or official source hook.
• Visible coverage limit and last checked date.

Read the three geographic layers separately

County, municipality and bidding area are separate objects in a decision file. The county can frame regional infrastructure and show which projects are covered. The municipality is the local planning geography and may have the plan archive, building office and environmental contacts relevant to a site. The bidding area is an electricity-market geography used to describe wholesale prices and transmission constraints. None replaces the others.

A map or table can show the relationships without turning them into a score. Falun belongs to Dalarna and SE3; Luleå to Norrbotten and SE1; Staffanstorp to Skåne and SE4. These labels help the reader place a source. They do not say how much power remains at a property, whether a plan allows a hall or whether a municipal body supports a project.

Keep the location accuracy in view as well. A county point is an orientation marker. A municipality point is not a site boundary. A district point is not a measured building footprint. The public launch set omits sensitive or undisclosed detail. Follow the project profile for the evidence behind a location rather than reading precision into the symbol.

1. County context.
2. Municipal planning and local public record.
3. Wholesale bidding area.
4. Location accuracy and project-specific source.

Use a geography file to ask better local questions

A good geography page is a reading aid for the next investigation. Read the summary, inspect the projects actually connected to the geography, open the official sources and then use the questions at the end. The questions should concern the concrete site: plan instrument, property rights, network owner, water, noise, access, neighbours and the evidence needed for a later decision.

Do not treat a project list as a site shortlist. A named operator may have an operating hall, a development target or a regional presence. A county with several project rows may have no public evidence of a common campus or common connection. Follow the project profile’s phase and capacity context, and keep announced, current, historic and unknown fields separate.

The same applies to local advantages. A geography page may describe public infrastructure, a company statement or a planning context. It should not turn that into “available power”, “build-ready land” or “municipal approval”. Those conclusions need property-level and authority-level documents. The page’s value is that it shows which documents would be needed.

• Which project rows actually sit in the geography?
• Which local plan and property documents are named?
• Which network owner and local authority would answer?
• Which conclusion is still outside the public file?

Keep gaps visible when coverage is uneven

Coverage will be uneven at launch because public evidence is uneven. Stockholm can have several operator pages while a northern municipality has one company record. A named project can have a stage but no public MW. A county can have a useful official link without a finished municipal dossier. These are different gaps and should be labelled separately.

When a reader asks why a place is not listed, the honest answer is the coverage state. DataCenterSweden has not published a reviewed file for that object, or the available source does not establish the requested fact. The answer should point to the broader methodology and to the official authority or network-owner door, not imply that the place has been rejected.

Do not solve uneven coverage by duplicating generic copy across municipalities or by assigning a capacity estimate to a county. A smaller set of traceable profiles is more useful than a complete-looking directory. New geography pages should be added only when they have a distinct local conclusion, sources and a clear relationship to actual projects or public planning material.

1. Label missing profile, missing source and missing fact separately.
2. Do not infer land, power, planning or political support from absence.
3. Avoid generic municipality pages and county MW estimates.
4. Add a geography only with a distinct sourced conclusion.