Sabey Data Centers Seattle
3311 South 120th Place
Parcel boundary
Recorded as in service.
Status inferred from osm footprint (Sep 8, 2026). No filing states it in as many words.
- Status
- Operating (inferred)
- Owner
- Sabey Data Centers
- Capacity
- not stated
- Location known to
- Parcel boundary
- County
- King County
- State
- Washington
- Electric utility
- Not identified
- Grid operator
- CAISO
Location and nearby
Sabey Data Centers Seattle is on record as operating in King County, Washington. 23 other campuses are on record within 25 miles, 5 of them within 5 miles. The nearest is 0.11 mi away.
Nearest of each kind: Operating 0.11 mi Permitted 24.0 mi
Nearest campuses on record
- 0.11 mi
Intergate Seattle East Building 1
Operating · King County, WA
- 0.19 mi
Intergate Seattle West Building C
Operating · King County, WA
- 0.22 mi
Operating · King County, WA
- 0.2 mi approximate
Operating · King County, WA
- 4.1 mi approximate
Operating · King County, WA
- 5.5 mi approximate
Operating · King County, WA
What is on record
Owner
Sabey Data Centers Strong
The chain
-
owner of record in government GIS layer
Sabey
WSDOT: Washington data centers (buildings) · Sep 8, 2026
Filed by: Sabey
Sources name more than one company here: Digital Realty, Sabey Data Centers. That usually means a building with tenants. No source we hold says which is the landlord, so we do not guess.
- Address on file
- 3311 South 120th Place
- Capacity
- not stated
- Building area
- 107,319 sq ft
- Diesel generators
- No air permit found in the records we collect
- Water
- Not collected. State water withdrawal permits are not in this build.
- Electric utility
- More than one utility serves this county, and no filing we hold names which one
- Also recorded as
- Digital Realty · Digital Realty Trust, Inc. · Intergate Seattle East Building 2 · Intergate Seattle East Building 3 · Intergate Seattle East Building 4 · Sabey and 1 more
Buildings and phases
4 distinct buildings, parcels or permits make up this campus.
| Name or address | Status | Permit | Area | Date |
|---|---|---|---|---|
| Intergate Seattle East Building 2 | Operating | not stated | not stated | Mar 27, 2024 |
| Intergate Seattle East Building 3 | Operating | not stated | not stated | Mar 28, 2024 |
| Intergate Seattle East Building 4 | Operating | not stated | not stated | Mar 28, 2024 |
| Sabey Data Centers Seattle | Operating | not stated | not stated | Sep 8, 2026 |
How the status changed
- Operating Mar 27, 2024 inferred
osm footprint
Overpass data_center query, tile conus-w1 bbox 24.0,-125.0,50.0,-115.0
- Operating Mar 28, 2024 inferred
osm footprint
Overpass data_center query, tile conus-w1 bbox 24.0,-125.0,50.0,-115.0
- Operating Mar 28, 2024 inferred
osm footprint
Overpass data_center query, tile conus-w1 bbox 24.0,-125.0,50.0,-115.0
- Operating Jun 14, 2026 inferred
DCE status 'mapped' (located only, single source)
- Operating Sep 8, 2026 inferred
WSDOT: Washington data centers (buildings): building
- Operating Sep 8, 2026 inferred
WSDOT: Washington data centers (buildings): building
- Operating Sep 8, 2026 inferred
WSDOT: Washington data centers (buildings): building
- Operating Sep 8, 2026 inferred
WSDOT: other Washington data centers:
- Operating Sep 8, 2026 inferred
Cleanview status 'Operating'
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)
About this data
Evidence
Primary record
A government filing, a federal permit, an assessor parcel or the operator’s own page.
Location known to
Parcel boundary
Matched to an assessor parcel, so the boundary is the parcel.
Independent sources
4
assessor parcel, directory, government record, osm footprint. Directories count once between them, because they copy each other.
Spotted something wrong? Tell us and we will fix it.
Where this comes from
10 source records back this page. Each row is a document we retrieved and kept, so a claim can be checked against the original.
| Document | Role | Row | Date |
|---|---|---|---|
| Overpass data_center query, tile conus-w1 bbox 24.0,-125.0,50.0,-115.0 US | Primary | osm=way/205724881 | Mar 27, 2024 stated in the file |
| Overpass data_center query, tile conus-w1 bbox 24.0,-125.0,50.0,-115.0 US | Primary | osm=way/293211686 | Mar 28, 2024 stated in the file |
| Overpass data_center query, tile conus-w1 bbox 24.0,-125.0,50.0,-115.0 US | Primary | osm=way/293211687 | Mar 28, 2024 stated in the file |
| WSDOT: Washington data centers (buildings) US-WA | Primary | OBJECTID=123 | Sep 8, 2026 retrieved by us |
| WSDOT: Washington data centers (buildings) US-WA | Primary | OBJECTID=222 | Sep 8, 2026 retrieved by us |
| WSDOT: Washington data centers (buildings) US-WA | Primary | OBJECTID=223 | Sep 8, 2026 retrieved by us |
| WSDOT: other Washington data centers US-WA | Primary | OBJECTID=5 | Sep 8, 2026 retrieved by us |
| Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US | Primary | id=1266 | Sep 8, 2026 retrieved by us |
| dce tracker export (© DataCentersExposed contributors, datacentersexposed.com, ODbL 1.0. Contains data © OpenStreetMap contributors.) US | Primary | slug=intergate-seattle-east-building-4-osmway-293211687 | Jun 14, 2026 last changed on the server |
| Washington statewide current parcels (WA Geoservices) (point queries) US-WA assessor parcel 033-1023049078, owner of record None, match pin_on_facility | Corroborating | query=47.49503,-122.29057 | Sep 9, 2026 retrieved by us |
Cleanview (cleanview.co) © DataCentersExposed contributors, datacentersexposed.com, ODbL 1.0. Contains data © OpenStreetMap contributors.
Free email alerts
Know first when a data center is recorded in King County
Each time we refresh the public records and a new campus appears in King County, you get one short email naming it, with the document behind it.