AWS Beech Road Building 1
BEECH RD NW
Parcel boundary
Someone has proposed it. Nothing has been approved and nothing is being built.
Status inferred from cleanview directory (Sep 8, 2026). No filing states it in as many words.
- Status
- Proposed (inferred)
- Owner
- Amazon (AWS)
- Capacity
- 76 MW directory claim
- Location known to
- Parcel boundary
- County
- Licking County
- State
- Ohio
- Electric utility
- Not identified
- Grid operator
- PJM
Location and nearby
AWS Beech Road Building 1 is on record as proposed in Licking County, Ohio. A directory lists its capacity at 76 MW; no filing we hold states a figure. 90 other campuses are on record within 25 miles, 45 of them within 5 miles. The nearest is 0.2 mi away, measured between approximate points.
Nearest of each kind: Operating 1.0 mi Under construction 2.0 mi Permitted 0.57 mi Proposed 0.2 mi
Nearest campuses on record
- 0.2 mi approximate
Johnstown Data Center (Beech Rd.)
Proposed · Licking County, OH
- 0.3 mi approximate
Karis Critical New Albany Data Center
Proposed · Licking County, OH
- 0.57 mi
Microsoft Licking County Campus 1
Permitted · Licking County, OH
- 0.9 mi approximate
New Albany Data Center - Socrates North
Proposed · Licking County, OH
- 1.0 mi
Operating · Licking County, OH
- 1.1 mi
Operating · Licking County, OH
What is on record
Owner
Amazon (AWS) Strong
The chain
-
assessor parcel owner of record
AMAZON DATA SERVICES INC
Central Ohio parcels (City of Columbus GIS, 7 counties) (point queries) · Sep 9, 2026
Filed by: AMAZON DATA SERVICES INC
- Address on file
- BEECH RD NW
- Capacity
- 76 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
- AWS Beech Road Building 10 · AWS Beech Road Building 11 · AWS Beech Road Building 12 · AWS Beech Road Building 13 · AWS Beech Road Building 14 · AWS Beech Road Building 2 and 15 more
How the status changed
- 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)
- 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)
- 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)
- 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)
- 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)
- 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
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. The point comes from a directory, which does not say how it was derived.
Independent sources
2
assessor parcel, directory. Directories count once between them, because they copy each other.
Spotted something wrong? Tell us and we will fix it.
Where this comes from
23 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 Licking County
Each time we refresh the public records and a new campus appears in Licking County, you get one short email naming it, with the document behind it.