Power by county
Johnson, TX: data center power outlook
Johnson, Texas is served through the ERCOT market (Electric Reliability Council of Texas), and the figures below describe the public grid around a prospective data center site there. Johnson carries 39 mapped substations within its boundary, and the highest reachable grid access is 345 kV. Service in Johnson spans 9 utilities, with DENTON COUNTY ELEC COOP, INC, HEART OF TEXAS ELECTRIC COOP, HILCO ELECTRIC COOPERATIVE, INC. among those mapped.
Grid position at a glance
- Serving utilities
- DENTON COUNTY ELEC COOP, INC, HEART OF TEXAS ELECTRIC COOP, HILCO ELECTRIC COOPERATIVE, INC., NAVARRO COUNTY ELEC COOP, INC, NAVASOTA VALLEY ELEC COOP, INC, ONCOR ELECTRIC DELIVERY COMPANY LLC, TEXAS-NEW MEXICO POWER CO, TRI-COUNTY ELECTRIC COOP, INC (TX), UNITED ELECTRIC COOP SERVICE INC - (TX)
- ISO / market
- ERCOT (Electric Reliability Council of Texas)
- Highest grid access
- 345 kV
- Substations in county
- 39
- Industrial retail rate
- 6.5¢/kWhState-level EIA-861 industrial average. The map colours by this, not by a per-county rate.
- Per-utility rates in county
- 7 of 9 serving utilities: 5.6 to 14.0¢/kWhLowest to highest industrial rate among the utilities serving this county (EIA-861 Sales to Ultimate Customers). A spread, not the county’s rate, and it covers only the serving utilities that report one.
- Interconnection queue
- 2 projects, 629 MW
- Proposed generation
- 773 MW planned or under constructionUnits filed with EIA as planned or under construction (Form EIA-860M). Declared intent from the federal inventory, not the interconnection queue and not guaranteed capacity.
- Grid carbon intensity
- 734 lb CO2/MWh
- Water withdrawals
- 13 Mgal/dAll uses, freshwater. Water already withdrawn locally, not water available for a new load.
- Construction labor near site
- 225,007 employed in construction within ~120 kmA large build needs hundreds of skilled construction workers on site for one to three years. A county with few of them within commuting range means bussing crews in, per diem, and housing, which is real cost and schedule risk. This counts people employed in construction within about a 120 km drive (BLS QCEW), summed across nearby counties. It is not labor known to be available: most are already committed to other projects, and no public data reveals who is free.
Grid conditions in Johnson
The material below frames Johnson, Texas for a prospective large load, drawing only on public sources. Grid access in Johnson extends to 345 kV, a high-voltage line class. The mapped layer packs 39 substations into Johnson, a dense spread of options.
Interconnection over Johnson runs through the ERCOT market (Electric Reliability Council of Texas) and its rules. For Johnson, the rate shown is the state industrial average of 6.5 cents per kWh (EIA-861), a state figure and not a county-specific one. Beneath that state average, the utilities serving Johnson that report an industrial rate span 7 of 9 serving utilities: 5.6 to 14.0¢/kWh, shown as context and never as the county rate.
The queue feeds show 2 projects for Johnson, totalling 628.53 MW of requested capacity. EIA-860M records 773 MW planned or under construction for Johnson. Johnson sits under a balancing authority that eGRID puts at 734.003 lb CO2 per MWh.
Johnson withdrew 12.58 million gallons per day for all uses in the USGS 2015 data, which counts demand, not headroom. About 225,007 people are employed in construction within a 120 km commute of Johnson (BLS QCEW), which frames staffing distance rather than free labour.
For Johnson, treat this as screening-grade county context useful for narrowing a search rather than settling a site. Taken together, the figures for Johnson, Texas describe the grid around a prospective site, drawn from public data with their gaps left visible on purpose. To move past screening in Johnson, Texas, a specific address needs its own interconnection study, which this page does not attempt. The figures for Johnson, Texas refresh as their public datasets do, and the exact sources and dates sit in the source log below this section.