Skip to the content
Data Centers Near Me
Operating (inferred) Berkeley County · SC

Google data center, Berkeley County, South Carolina

Berkeley County, South Carolina

Building outline

Recorded as in service.

Status inferred from osm footprint (Sep 9, 2026). No filing states it in as many words.

Get directions
Drawn at the mapped building outline. Other campuses on record nearby are drawn around it.
Status
Operating (inferred)
Owner
Google
Capacity
34 MW directory claim
Location known to
Building outline
County
Berkeley County
State
South Carolina
Electric utility
Not identified
Grid operator
not stated

Location and nearby

Google data center, Berkeley County, South Carolina is on record as operating in Berkeley County, South Carolina. A directory lists its capacity at 34 MW; no filing we hold states a figure. 7 other campuses are on record within 25 miles, 2 of them within 5 miles. The nearest is 0.8 mi away, measured between approximate points.

Nearest of each kind: Operating 6.8 mi Under construction 16.2 mi Permitted 1.4 mi Proposed 0.8 mi

Nearest campuses on record

What is on record

Owner

Google Confirmed

The chain
  1. google first-party locations page lists this site

    Google

    Google data center locations page (first party) · Sep 9, 2026

Filed by: Google

Capacity
34 MW as reported by cleanview, not from a filing
Diesel generators
No air permit found in the records we collect
Water
2,740,055 gallons a year
Electric utility
More than one utility serves this county, and no filing we hold names which one
Also recorded as
Alphabet Inc. · Google · Google Berkeley County Data Center · Google LLC · Google Moncks Corner - Building 1 · Google Moncks Corner - Building 2 and 8 more

Buildings and phases

10 distinct buildings, parcels or permits make up this campus.

Name or address Status Permit Area Date
Google data center Operating not stated not stated Feb 19, 2024
Google Operating not stated not stated Feb 19, 2024
Google Operating not stated not stated Feb 19, 2024
Google Operating not stated not stated Feb 19, 2024
Google Operating not stated not stated Feb 19, 2024
Google Operating not stated not stated Feb 19, 2024
Google Operating not stated not stated Feb 19, 2024
Google Operating not stated not stated Feb 19, 2024
Google Operating not stated not stated Feb 19, 2024
Google Berkeley County Data Center Operating not stated not stated Jan 26, 2026

How the status changed

  1. Operating Feb 19, 2024 inferred

    osm footprint

    Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0

  2. Operating Feb 19, 2024 inferred

    osm footprint

    Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0

  3. Operating Feb 19, 2024 inferred

    osm footprint

    Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0

  4. Operating Feb 19, 2024 inferred

    osm footprint

    Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0

  5. Operating Feb 19, 2024 inferred

    osm footprint

    Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0

  6. Operating Feb 19, 2024 inferred

    osm footprint

    Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0

  7. Operating Feb 19, 2024 inferred

    osm footprint

    Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0

  8. Operating Feb 19, 2024 inferred

    osm footprint

    Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0

  9. Operating Feb 19, 2024 inferred

    osm footprint

    Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0

  10. Operating Jan 26, 2026 inferred

    osm footprint

    Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0

  11. Operating Jun 14, 2026 inferred

    DCE status 'mapped' (located only, single source)

    dce tracker export (© DataCentersExposed contributors, datacentersexposed.com, ODbL 1.0. Contains data © OpenStreetMap contributors.)

  12. Operating Sep 8, 2026 inferred

    Cleanview status 'Operating'

    Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)

  13. Operating Sep 8, 2026 inferred

    Cleanview status 'Operating'

    Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)

  14. Operating Sep 8, 2026 inferred

    Cleanview status 'Operating'

    Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)

  15. Operating Sep 8, 2026 inferred

    Cleanview status 'Operating'

    Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)

  16. Operating Sep 8, 2026 inferred

    Cleanview status 'Operating'

    Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)

  17. Operating Sep 8, 2026 inferred

    Cleanview status 'Operating'

    Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)

  18. Operating Sep 8, 2026 inferred

    Cleanview status 'Operating'

    Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)

  19. Operating Sep 8, 2026 inferred

    Cleanview status 'Operating'

    Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)

  20. Operating Sep 8, 2026 inferred

    Cleanview status 'Operating'

    Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)

  21. Operating Sep 9, 2026 inferred

    Google locations page; county-level placement

    Google data center locations page (first party)

About this data

Evidence

Primary record

A government filing, a federal permit, an assessor parcel or the operator’s own page.

Location known to

Building outline

A mapped building outline.

Independent sources

3

directory, first party, osm footprint. Directories count once between them, because they copy each other.

How we build this

Spotted something wrong? Tell us and we will fix it.

Where this comes from

21 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-e1 bbox 24.0,-85.0,50.0,-75.0 US Primary osm=way/1069388067 Feb 19, 2024 stated in the file
Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0 US Primary osm=way/1069388075 Feb 19, 2024 stated in the file
Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0 US Primary osm=way/1069388095 Feb 19, 2024 stated in the file
Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0 US Primary osm=way/1069388141 Feb 19, 2024 stated in the file
Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0 US Primary osm=way/1069388147 Feb 19, 2024 stated in the file
Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0 US Primary osm=way/1069388156 Feb 19, 2024 stated in the file
Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0 US Primary osm=way/1069388186 Feb 19, 2024 stated in the file
Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0 US Primary osm=way/1069388211 Feb 19, 2024 stated in the file
Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0 US Primary osm=way/610827836 Feb 19, 2024 stated in the file
Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0 US Primary osm=way/626226408 Jan 26, 2026 stated in the file
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=4046 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=4047 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=4048 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=4049 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=4050 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=4051 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=4052 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=4053 Sep 8, 2026 retrieved by us
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US Primary id=4054 Sep 8, 2026 retrieved by us
dce tracker export (© DataCentersExposed contributors, datacentersexposed.com, ODbL 1.0. Contains data © OpenStreetMap contributors.) US Primary slug=google-osmway-1069388075 Jun 14, 2026 last changed on the server
Google data center locations page (first party) US Primary location=Berkeley County, South Carolina Sep 9, 2026 retrieved by us

Cleanview (cleanview.co) © DataCentersExposed contributors, datacentersexposed.com, ODbL 1.0. Contains data © OpenStreetMap contributors. Google first-party locations page

Free email alerts

Know first when a data center is recorded in Berkeley County

Each time we refresh the public records and a new campus appears in Berkeley County, you get one short email naming it, with the document behind it.

Explore more