Google Barber County Data Center
Barber County commissioners approved an agreement with Google for a data center project on 2026-08-31. It is reported; the record holds no sourced date for when it reached that stage.
How much power it needs, how much water it would use and who would use it have not been disclosed.
How to read this page. Every fact links to the source it rests on; a number in brackets is its place in the source list. A figure no source gives reads Not disclosed, and nothing is estimated. Where sources give different figures, each is shown with who gave it, and another source's figure never stands in for the record's own. Entries are added and never overwritten; corrections are listed under What happened.
What is known
Each figure as its source gave it. The number in brackets is its place in the source list.
- Land
- Not disclosed
- Power it would draw
- Not disclosed
- Water
- Not disclosed
- Who leads it
- as stated by the source
- Who would use it
- Not disclosed
- Jobs once it runs
- Not disclosed
- Tax each year
- Not disclosed
Every field, with who said it and when (Researcher view)
Impact figures
| Field | Value | Who says so | Source | Last verified |
|---|---|---|---|---|
| How much power it needs | Not disclosed | |||
| How much water it would use | Not disclosed | |||
| How loud it would be | Not disclosed | |||
| Jobs once it runs | Not disclosed | |||
| Tax it would pay each year | Not disclosed |
The record's fields
| Field | Value | Who says so | Source | Last verified |
|---|---|---|---|---|
| Who is building it | as stated by the source | September 17, 2026 | ||
| Who is constructing it | Not disclosed | |||
| How much land | Not disclosed | |||
| Where its power comes from | Not disclosed | |||
| Grid connection | Not disclosed | |||
| How it is cooled | Not disclosed |
The developer's figure is what the company said; what a permit allows is the ceiling a permit sets; measured means observed. Water is in gallons a day or a year, whichever the source stated; a tax claim given as a range shows both ends, each linked to the source that gave it.
Still not public, and where it would show up
The record adds each the day a source gives it. Why these documents.
- Water useA state water right filing or a water supply agreement.
- Who would use itA lease announcement or a tenant named in a filing.
- Power the campus would drawA utility or public service commission docket, an interconnection filing, or an air permit for an on site plant.
- Jobs and taxAn incentive agreement, a county's economic development filing or a fiscal note.
What was decided
Acts of Barber County and the cities in it about data centers, on the record with their source. A rule about the area is not a decision about this record.
| Date | Who | Decision | Source |
|---|---|---|---|
| Barber County | Barber County approved Google two million square foot data center with $320 million revenues over 20 years | prospect.org | |
| Barber County | The vote passed 2-0 with one commissioner abstaining | kake.com | |
| Barber County | Barber County commissioners approved a 1.7 million square foot Google data center | kake.com |
What happened
No dated entry is on the record yet.
22 corrections to this record
Every correction, with its reason
-
· the status of a projects row
The stage was set by timeline entries that were returned to draft on 2026-09-17 (they had been published onto the record while it was still a draft skeleton). With no published entry behind it the record reads rumored until one is approved. The old and new text.
-
· the kind of source of a history entry
The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.
-
· the kind of source of a history entry
The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.
-
· the kind of source of a history entry
The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.
-
· the kind of source of a history entry
The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.
-
· the kind of source of a history entry
The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.
-
· the kind of source of a history entry
The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.
-
· the kind of source of a history entry
The source was labeled with the Google News search that found it; it now carries its outlet's tier (the record's rules of 2026-09-23). The link did not change. The day's label corrections.
-
· the kind of source of a history entry
Tier after resolution (2026-09-21). The source on file is kake.com, the publisher's own page. The item reached the record through Google News: "data center" Kansas, which the record carries at tier 1, and the approve copied the feed's tier onto this row. The tier now comes from the outlet, which the record already carries at tier 4 on 1 row of sources. DECISIONS section 7. The speaker, the claim, the date and the url are unchanged. The day's label corrections.
-
· the kind of source of a history entry
Tier after resolution (2026-09-21). The source on file is kake.com, the publisher's own page. The item reached the record through Google News: "data center" Kansas, which the record carries at tier 1, and the approve copied the feed's tier onto this row. The tier now comes from the outlet, which the record already carries at tier 4 on 1 row of sources. DECISIONS section 7. The speaker, the claim, the date and the url are unchanged. The day's label corrections.
-
· the kind of source of a history entry
Tier after resolution (2026-09-21). The source on file is kake.com, the publisher's own page. The item reached the record through Google News: "data center" Kansas, which the record carries at tier 1, and the approve copied the feed's tier onto this row. The tier now comes from the outlet, which the record already carries at tier 4 on 1 row of sources. DECISIONS section 7. The speaker, the claim, the date and the url are unchanged. The day's label corrections.
-
· the kind of source of a history entry
Tier after resolution (2026-09-21). The source on file is kake.com, the publisher's own page. The item reached the record through Google News: "data center" Kansas, which the record carries at tier 1, and the approve copied the feed's tier onto this row. The tier now comes from the outlet, which the record already carries at tier 4 on 1 row of sources. DECISIONS section 7. The speaker, the claim, the date and the url are unchanged. The day's label corrections.
-
· the kind of source of a history entry
Tier after resolution (2026-09-21). The source on file is kake.com, the publisher's own page. The item reached the record through Google News: "data center" Kansas, which the record carries at tier 1, and the approve copied the feed's tier onto this row, from the wrapper https://news.google.com/rss/articles/CBMizgFBVV95cUxNRTNLQ1E1YU52djZPSndUekZDZzV1WVRtOFJ2bEg2SUtQcWJmU3k3NktrMUo1b1BZdE1CdDJFOS1RSTJYS1RXbHdJQ1I3WWFHWUxBMTJXV3hyOGxtRWxGVWhSSG9HcTlRZE93Q0stQ1FZQlQ0YnFSN1FMaERvZU9xT09OYVY4TWx3ak0xQlNEVnQzcXJtdjdYeldjUzQxUUJoS1NXZVZnaW9WTHNoNkg5VnBLaWNTaF9tYW5pbks5N3EtYWg2OTBnalBSN0Rzdw. The tier now comes from the outlet, which the record already carries at tier 4 on 1 row of sources. DECISIONS section 7. The speaker, the claim, the date and the url are unchanged. The day's label corrections.
-
· the kind of source of a history entry
Tier after resolution (2026-09-21). The source on file is kake.com, the publisher's own page. The item reached the record through Google News: "data center" Kansas, which the record carries at tier 1, and the approve copied the feed's tier onto this row. The tier now comes from the outlet, which the record already carries at tier 4 on 1 row of sources. DECISIONS section 7. The speaker, the claim, the date and the url are unchanged. The day's label corrections.
-
· the kind of source of a history entry
Tier after resolution (2026-09-21). The source on file is kake.com, the publisher's own page. The item reached the record through Google News: "data center" Kansas, which the record carries at tier 1, and the approve copied the feed's tier onto this row. The tier now comes from the outlet, which the record already carries at tier 4 on 1 row of sources. DECISIONS section 7. The speaker, the claim, the date and the url are unchanged. The day's label corrections.
-
· the draft of a status history row
Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval. The old and new text.
-
· the draft of a status history row
Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval. The old and new text.
-
· the draft of a status history row
Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval. The old and new text.
-
· the draft of a status history row
Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval. The old and new text.
-
· the draft of a status history row
Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval. The old and new text.
-
· the draft of a status history row
Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval. The old and new text.
-
· the draft of a status history row
Published on a project that was still a draft skeleton and still short of the record's skeleton minimum rule; returned to draft on 2026-09-17 pending the project meeting the rule or a person's approval. The old and new text.
Every correction on the record is on the corrections page.
The site
Where in Barber County is not in the public record. The pin marks the county seat, not a building, and the outline is the county.
Tap a pin for the data center, the parcel for its record
- This record: Proposed, ringed
- data center
- Dashed edge: the exact site is not in the public record
- Smaller pins: 5 other published records in Kansas
Details
- this record's location, ringed
- parcel outline, from the county parcel record
- city limits, U.S. Census Bureau, on a town level record
- county boundary
The other pins are the published projects in the same state, each in its stage color. The imagery beneath is the USGS national orthoimagery, public domain, shown so the land around the site can be read.
- Where
- Barber County, Kansas
- How exactly it is located
- County level, the county seat
- The parcel
- No parcel outline in the public record
- Nearest homes
- Not computed for a record placed at a place center
- Nearest records
- Nearest records are not computed for a record placed at a county seat.
Questions about this project
4 questions answered from the record
Who is building Google Barber County Data Center?
-
Google is the developer. No construction contractor is named on the record yet.
How much power and water does Google Barber County Data Center say it needs?
-
Power: not disclosed by any source on file. Water: not disclosed by any source on file.
Where does Google Barber County Data Center stand today?
-
It is reported; the date it reached that stage is not sourced, only the day a page was read. No dated entry is on the record yet.
What has Barber County decided about it?
-
Barber County: Barber County approved Google two million square foot data center with $320 million revenues over 20 years (reported September 21, 2026, source); and Barber County: The vote passed 2-0 with one commissioner abstaining (reported August 31, 2026, source). 3 events are on the county's rows; a rule about the area is not a decision about this record.
Sources
Reporting
- Barber County finalizes deal with Google for data center project - kake.com, kake.com, August 31, 2026, local outlet
- Google’s massive data center approved in Barber County amidst public concern - KSN.com, KSN.com, August 31, 2026, local outlet
- Commissioners approve Google data center in Barber County - kake.com, kake.com, August 31, 2026, local outlet
- Barber County Commission approves agreement for Google data center - KWCH, KWCH, August 31, 2026, local outlet
- Kansas residents pleading for more transparency amid Google data center project - KAKE, KAKE, September 14, 2026, local outlet
- Barber County commissioners will meet to finalize Google data center - KWCH, KWCH, August 31, 2026, local outlet
- Commissioners approve Google data center in Barber County | Trusted News Source for Wichita & Kansas - kake.com, kake.com, August 31, 2026, local outlet
- Barber County finalizes deal with Google for data center project | Trusted News Source for Wichita & Kansas - kake.com, kake.com, August 31, 2026, local outlet
8 sources on file.
Cite this record
Data Center Record, "Google Barber County Data Center", https://datacenterrecord.org/projects/google-barber-county-data-center-ks, last verified September 17, 2026.
Cite this page
Data Center Record, "Google Barber County Data Center", https://datacenterrecord.org/projects/google-barber-county-data-center-ks. Data: Data Center Record, datacenterrecord.org, CC BY 4.0.
The structured rows are CC BY 4.0. Link to this page; that is what turns a reuse into a citation. Prose stays under copyright.
For researchers
- Slug
- google-barber-county-data-center-ks
- Status value
- rumored
- Stage
- Proposed
- Tier
- skeleton
- Tags
- skeleton
- Place id
- us/ks/barber-county
- Coordinates
- 37.28444, -98.58111
- Location precision
- county
- Location source
- County seat (Medicine Lodge), Wikidata, placed at county level
- Coordinate source
- wikidata county seat
- Location source number
- Not disclosed
- Location last verified
- September 16, 2026
- EPA registry id
- Not disclosed
- Use type values
- not_disclosed
- Tenancy value
- not_disclosed
- Cooling type value
- not_disclosed
- Capacity basis
- not_disclosed
- Water basis
- not_disclosed, gallons_per_day
- Acreage basis
- Not disclosed
- Interconnection value
- not_disclosed
- Capacity, if disclosed
- Not disclosed
- Rating of the county's rows
- Not disclosed
- Published
- 2026-09-05
- Last verified
- 2026-09-17