Stargate Abilene - Building 1
Taylor County, Texas
Building outline
Recorded as in service.
Status inferred from osm footprint (Sep 8, 2026). No filing states it in as many words.
- Status
- Operating (inferred)
- Owner
- Owner not resolved
- Capacity
- 150 MW directory claim
- Location known to
- Building outline
- County
- Taylor County
- State
- Texas
- Electric utility
- Not identified
- Grid operator
- ERCOT
Location and nearby
Stargate Abilene - Building 1 is on record as operating in Taylor County, Texas. A directory lists its capacity at 150 MW; no filing we hold states a figure. 9 other campuses are on record within 25 miles, 5 of them within 5 miles. The nearest is 0.41 mi away.
Nearest of each kind: Operating 0.88 mi Under construction 12.8 mi Permitted 0.41 mi Proposed 1.0 mi
Nearest campuses on record
- 0.41 mi
Permitted · Taylor County, TX
- 0.88 mi
Operating · Taylor County, TX
- 1.0 mi approximate
Crusoe Abilene - Building 9 (Microsoft)
Proposed · Taylor County, TX
- 4.4 mi approximate
Stargate Abilene (Lancium Clean Campus)
Operating · Taylor County, TX
- 4.7 mi approximate
Permitted · Taylor County, TX
- 8.6 mi approximate
Proposed · Taylor County, TX
What is on record
Owner
Owner not resolved
- Capacity
- 150 MW as reported by cleanview, not from a filing
- 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
- Stargate Abilene - Building 2 · Stargate Abilene - Building 3 · Stargate Abilene - Building 4 · Stargate Abilene - Building 5 · Stargate Abilene - Building 6 · Unnamed data center (way/1472056705) and 29 more
Buildings and phases
30 distinct buildings, parcels or permits make up this campus.
| Name or address | Status | Permit | Area | Date |
|---|---|---|---|---|
| Unnamed data center (way/1472056705) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1472056706) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1472056707) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1472056708) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1472056709) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1472056710) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1472056711) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1472056712) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1472056713) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1472056714) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1530966366) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1530966367) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1530966368) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1530966369) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1530966370) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1530966371) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1530966372) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1530966373) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1530966374) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1530966375) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1530966376) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1530966377) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1530966378) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1530966379) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1530966380) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1530966381) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1530966382) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1530966383) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1530966384) | Operating | not stated | not stated | Jun 20, 2026 |
| Unnamed data center (way/1530966385) | Operating | not stated | not stated | Jun 20, 2026 |
How the status changed
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Jun 20, 2026 inferred
osm footprint
Overpass data_center query, tile conus-c1 bbox 24.0,-105.0,50.0,-95.0
- Operating Sep 8, 2026 inferred
Cleanview status 'Operating'
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)
- Operating Sep 8, 2026 inferred
Cleanview status 'Operating'
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)
- Proposed Sep 8, 2026 inferred
Cleanview status 'Planned'
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)
- Proposed Sep 8, 2026 inferred
Cleanview status 'Planned'
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)
- Proposed Sep 8, 2026 inferred
Cleanview status 'Planned'
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)
- Proposed Sep 8, 2026 inferred
Cleanview status 'Planned'
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)
About this data
Evidence
Map footprint and directories
An OpenStreetMap footprint plus one or more directories. No filing behind it.
Location known to
Building outline
A mapped building outline.
Independent sources
2
directory, 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
36 source records back this page. Each row is a document we retrieved and kept, so a claim can be checked against the original.
Cleanview (cleanview.co)
Free email alerts
Know first when a data center is recorded in Taylor County
Each time we refresh the public records and a new campus appears in Taylor County, you get one short email naming it, with the document behind it.