Facility or project event · Rezoning approved · Official record
Rezoning approved on 21 April 2026: AL Bessemer Land Data Center Project (Bessemer, AL) — city ordinance dated 21 April 2026
The Bessemer City Council adopted, and the Mayor approved, Ordinance No. 3698 on April 21, 2026, rezoning the property in AL Bessemer Land, LLC's application from A-1 vacant Agricultural to I-1 Light Industrial for construction and operation of a multi-phased data center.
- Event date
- 'ADOPTED this the 21st day of April 2026' (Council President) and 'APPROVED this the 21st day of April 2026' (Mayor).
- Source dated
- The ordinance is dated by its printed adoption and approval lines, 21 April 2026; the Jefferson County Judge of Probate recorded it on 28 April 2026.
- Source accessed
- Retrieved by DataCenterData; not an event date.
- Added to Latest updates
- When this entry entered the updates log; not an event date.
- Event type
- Rezoning approved · Approvals
- Evidence basis
- Official record · Bessemer City Council
- Confidence
- HighSigned, recorded ordinance text states the action, date and applicant.
- State
- Alabama
- Linked records
- AL Bessemer Land Data Center Project
al-bessemer-land-data-center - Linked claims
- None linked
What the source says
WHEREAS, AL Bessemer Land, LLC c/o Martin Evans, Agent for (Owner) ... filed an application to re-zone ... for construction and operation of a multi-phased data center ... ADOPTED this the 21st day of April 2026.
Where: Page 1 first WHEREAS clause; page 2 'ADOPTED' line; page 3 'APPROVED' line (scanned document). The PDF is linked from the Bessemer City Clerk page, bessemeral.org/departments/city-clerk.
Source: City of Bessemer Ordinance No. 3698 (AL Bessemer Land LLC Rezoning Ordinance)
Internet Archive copy (captured 21 September 2026)
What this does not establish
- construction
- building permits
- operation
Still unknown
- council vote tally
- end user or operator
- building permit or construction start
- IT and utility capacity
Identifiers
Event ID 017f39134747bf56d66a0d64462e8fab558be20636a4e3de5d3168a31f81fa30. The ID is derived from the event itself and never changes. A later correction would be published as a separate, linked entry.