Explore Sweden

Four doors

Use the four doors as filters on one file, not as four separate libraries. The map is useful for orientation once a municipality is published. The tracker is the object you can sort, cite and crawl. Location files exist only where a reviewed paragraph and at least one related project or official hook already sit. Company pages begin with actors attached to those projects; they are not a national operator census.

AWS Europe (Stockholm) appears in the tracker without a map pin, because AWS did not publish a municipality on the cited launch pages. Hydro66 in Boden is pinned at municipality accuracy from a company-registry locality, not from a surveyed building outline. Those two cases are the rule, not exceptions: location accuracy follows the source, and undisclosed coordinates stay off the map.

• Map — schematic, with a list.
• Projects — filterable tracker.
• Locations — counties and municipalities with files.
• Companies — operators and developers on those projects.

Coverage edges

A missing municipality is a missing reviewed file, not a finding that the municipality has no opportunity. Equinix SK3 is named on the operator hub but does not yet have its own profile. Other Bahnhof and Conapto halls are not each given a launch page. Östersund is left out after EcoDC reported discontinuation. Those gaps stay visible instead of being filled with directory megawatts or invented counties.

Use the register as a set of evidence doors

Explore is not a claim that every Swedish data center is listed. It is the starting point for the public records that have been reviewed for this launch. The map is a schematic orientation layer. The project tracker is the crawlable list. Location pages are published files with their own sources. Company pages begin with actors already attached to the projects in the register. Each door has a different coverage rule, and a record can be strong in one door while incomplete in another.

Start by deciding what you need to know. If you need names and stages, use the project tracker. If you need spatial orientation, open the map and read the location-accuracy note. If you need local planning questions, open the municipality or county file and then follow its sources. If you need an actor, open the company profile and inspect its documented role. Do not use the map as a substitute for the source list or the project profile.

The register deliberately leaves gaps visible. An undisclosed municipality is not turned into a guessed pin. A project named in a regional launch can appear in the tracker without a location marker when the cited source does not identify a municipality. A missing municipality profile means that DataCenterSweden has not completed a publishable file; it does not mean that the municipality has no data center opportunity.

• Map — approximate public locations and a visual legend.
• Tracker — projects, stages, actors and capacity context.
• Locations — reviewed county or municipality files only.
• Companies — documented roles attached to published projects.

Read pins and filters without over-reading them

A pin represents the accuracy that the source supports, not a surveyed building outline. A municipality-accuracy pin can cover a large area. A district pin is still not a plot boundary. An undisclosed location stays off the map. The list beside the map is therefore essential: it carries the project name, stage and link to the profile, while the map supplies orientation. When a pin is selected, inspect the profile and its location note before drawing a site conclusion.

The tracker filters answer register questions. Search matches project, municipality and actor text. The stage filter narrows the project-level development label. Sorting by latest material update orders records by the date in the data, not by a promise that the project is more advanced. Sorting by name is simply alphabetical. A result of zero means that no published record matches the selected filter combination; it does not mean that no data center exists in the geography.

Capacity needs its own reading step. A number must be read with metric type, context and year. A current 41 MW statement, an announced 300 MW site-power plan and a historic 120 MW energy-need sentence are not interchangeable. Unknown values remain unknown and are not sorted or displayed as zero. Use the project profile and methodology links when the table cell is not enough.

1. Location accuracy and source note read before using a pin.
2. Stage filter distinguished from planning, grid and permit status.
3. Sort order understood as register ordering, not an investment ranking.
4. Capacity metric, context and year read together.

Keep county, municipality and bidding area separate

A county file, a municipality file and an electricity-area reference answer different questions. The county describes a regional frame and the projects that the register has actually connected to it. The municipality file focuses on the local public record. SE1, SE2, SE3 and SE4 are wholesale-market areas. They are not counties, planning authorities or allocations of connection capacity to a plot.

A place can belong to one county and municipality while the electricity area adds another system boundary. Luleå and Boden are in the northern SE1 context, while Sollefteå is in Västernorrland and SE2. Falun is in Dalarna and SE3. Staffanstorp and Falkenberg are in SE4. These relationships help readers orientate the source material; they do not create a combined campus or a regional MW total.

Read the geographic file before reusing its language. A county page can say which public infrastructure or projects are documented without saying that all land is available. A municipality page can list planning questions without endorsing an operator. A bidding-area page can explain wholesale constraints without answering the network owner’s property-level connection question. Keep the object named beside every conclusion.

• County — regional context and published project coverage.
• Municipality — local planning, public records and local questions.
• Bidding area — wholesale-market geography.
• Network owner — property-level connection counterpart.

Turn a coverage gap into a next source request

When a record is missing, identify what is missing: a source, a reviewed paragraph, a municipality, a project identity, a capacity definition or a current stage. Do not fill the gap with a directory number or a nearby project. A regional page can be a lead to investigate, but it is not automatically a publishable profile. The launch set prefers fewer records with a visible evidence trail.

For a project, the next request may be an operator page, a dated report, a municipal plan document or a network-owner response. For a geography, it may be a local plan archive, an official infrastructure source or a project document that actually names the municipality. For a company, it may be an official role or ownership source. Record the date and the exact claim the new source would support.

The Explore page is successful when the reader can move from a broad question to the right evidence without confusing the layers. Open the tracker for the set of records, the profile for facts and gaps, the geography file for local context, and the methodology page for definitions. If no page closes the question, say what remains unknown and who would have to answer it.

1. Name the missing object or field.
2. Choose a source that can support that exact claim.
3. Keep nearby projects, directories and regional context separate.
4. Publish fewer records rather than a guessed complete map.