Edge and micro sites versus hyperscale in Sweden

Reading order

Name the scale object before you name the marketing object. An inner-city colo hall, a metro campus, a cloud region, a municipal hyperscale campus and a mega-site announcement are five sizes. Write who owns the IT load and whether several customers share the room. Then write whether any megawatt is IT, facility, site, utility or unclear. “Edge” that only means “not 300 MW” is not a classification you can store.

Then name the connectivity object. Netnod’s exchange pages and PTS mapping are official starting points for Swedish interconnection and coverage. They do not place a micro hall on a cadastral unit. A Stockholm meet-me-room sentence does not travel to Sollefteå. The inland-backhaul page holds that warning.

Then name what is unpublished. AWS did not pin its Stockholm Availability Zones to municipalities. This register has not found a Stockholm Local Zone on the cited AWS location pages. Do not invent one. Do not invent a national micro-site count from Pionen plus Bunker plus a Kista colo campus.

• Scale object before marketing object.
• IT owner and shared room named.
• Every megawatt labelled — or left empty.
• A Local Zone in another city is not a Stockholm pin.

What the scale words actually change

A cloud Region is a product geography, not a hall census. AWS’s 12 December 2018 Europe (Stockholm) page and the matching press release describe three Availability Zones and a low-latency claim toward Nordic end users. They do not publish a millisecond figure and they do not name municipalities. Europe (Stockholm) is already a Region. A Local Zone, on the cited AWS pages, is an extra city with a parent Region — not a relabel of those three Stockholm zones.

Local Zones stay on their own rows. The product locations page lists more than 30 metropolitan areas and names Oslo with parent region Europe (Stockholm). The available-Local-Zones documentation table lists Copenhagen and Helsinki under eu-north-1. This register has not found a Stockholm Local Zone on those pages. The 1 July 2026 Athens Local Zone news is a different city under a different parent Region. It is not a Swedish micro-site.

Urban halls and mega-site announcements can share a country without sharing a class. Equinix SK1 and SK2 and Digital Realty’s Stockholm campus are metro colo pages. Bahnhof Pionen is an inner-Stockholm hall without a megawatt on the cited colo pages. Bahnhof’s 21 January 2026 Bunker page is a Gothenburg specification: 6,000 square metres, 12 MW total power capacity, direct water cooling — a specification, not a commissioning certificate and not a Pionen megawatt. atNorth SWE01 states 12 MW site power in the Stockholm metro. The 29 January 2026 SWE02 notice states 30 MW. The 23 February 2026 SWE04 notice states a 300 MW mega site in Sollefteå. STACK’s live STO01 page states 18 MW, eight acres and one building. Those remain dated operator rows.

Owner-occupied and fibre files stay labelled. Meta’s Luleå page is an operating northern campus. Microsoft’s 16 November 2021 region named Gävle, Sandviken and Staffanstorp without facility megawatts. Google’s 2 June 2026 Horndal groundbreaking is a land-and-construction step. PTS’s MTBBK reports map Swedish broadband and backbone. Netnod publishes exchanges in Stockholm, Gothenburg, Sundsvall–Gävle and Luleå. An exchange is an exchange. A hall next to one is still a hall. Conapto’s 24 June 2026 CoreWeave notice and the 24 October 2025 +8 MW expansion are Stockholm-area colo events. They do not convert those halls into Local Zones.

What named primary sources show

AWS’s 12 December 2018 Region page and press release remain the dated Sweden-region opening. The Local Zones locations page and the available-Local-Zones table are the dated neighbour-city product facts: Oslo, Copenhagen and Helsinki, not a Stockholm Local Zone. The Athens 1 July 2026 news page stays a different city.

Urban and campus rows stay on operator pages. Equinix Stockholm / SK1 / SK2 and Digital Realty Stockholm are metro colo. Bahnhof’s colo and Pionen pages are inner-Stockholm product pages. The 21 January 2026 Bunker page is a Gothenburg specification at 12 MW total power. atNorth SWE01, SWE02 and SWE04 are 12 MW, 30 MW and 300 MW operator sentences. STACK STO01 is 18 MW on the live campus page. Meta Luleå, Microsoft 2021 and Google Horndal 2 June 2026 are owner-occupied or region files.

Fibre and exchange: PTS MTBBK and Netnod’s four named IX cities. Related long pages: the types page, the colo-versus-build-to-suit page, connectivity and inland backhaul. None of those pages is a Swedish micro-site census.

A matrix instead of a Swedish edge score

Draw scale classes in rows and evidence in columns. Region, Local Zone, urban hall, metro campus, mega-site announcement, owner-occupied campus and an IX are different rows. Product page, dated news, specification and operating hall are different columns. Empty cells stay empty. A latency slogan is not a column.

Do not invent a Swedish micro-count. Do not invent municipal pins for the 2018 Region. Do not treat 300 MW as the only real class, or a bunker specification as a live Local Zone.

Common misreads

The first misread is “Sweden has no edge.” The cited pages name urban halls and a Stockholm Region with three AZ. They do not publish a national micro-site census — and they do not prove the opposite either. The second is “Europe (Stockholm) is a Local Zone.” The 2018 page is a Region. Local Zones on the cited AWS pages are additional cities.

The third is “SWE04 300 MW means smaller Swedish halls are not real.” SWE01 is still 12 MW on the cited page. Equinix and Bahnhof pages still describe metro halls. The fourth is “next to a Netnod IX equals edge,” or that Conapto, Equinix, Bahnhof or STACK pages are Local Zones. The fifth is to treat the Gothenburg Bunker specification as an operating Stockholm hall or as a commissioned 12 MW IT load.

What to ask next

Ask whether the service is a Region AZ, a Local Zone in a named other city, or a colo hall that is not a Local Zone at all. Ask which path and which exchange hops sit between the users and the rack — and whether any millisecond figure is on a contract. Ask which megawatt figure is on the live cited page, and which cell is blank.

Then open the types page, the colo-versus-build-to-suit page, connectivity and inland backhaul. If the operator will not name the scale class, record the gap. Do not fill it from a latency slogan or from a 300 MW news page.

1. Region, Local Zone or colo hall named.
2. Path and exchange hops asked — ms only if contracted.
3. Every MW labelled from the live page.
4. Bunker kept as a Gothenburg specification.
5. No invented Swedish micro-census.

What this does and does not prove

This page proves that Swedish files already show more than one scale class, and that a Region is not a Local Zone. It proves that AWS opened Europe (Stockholm) with three AZ in 2018, that cited Local Zone pages name Oslo, Copenhagen and Helsinki rather than Stockholm, and that operator pages name both metro halls and a 300 MW Sollefteå announcement.

It does not prove a Swedish micro-site census or a latency table. It does not invent municipal pins, a Stockholm Local Zone, or a commissioned Bunker IT load. It does not treat an IX as a hall. It does not convert colo pages into Local Zones.

Unknown pins and unknown millisecond figures stay unknown. Point to the named source gap. Until a later primary source names a Stockholm Local Zone or a national micro-count, the matrix is a matrix.