Power by county
Wasco, OR: data center power outlook
Wasco, Oregon is served through an area outside an organized wholesale market, and the figures below describe the public grid around a prospective data center site there. Wasco carries 31 mapped substations within its boundary, and the highest reachable grid access is 1,000 kV. Service in Wasco spans 9 utilities, with BONNEVILLE POWER ADMINISTRATION, CENTRAL ELECTRIC COOP INC - (OR), CONSUMERS POWER, INC among those mapped.
Grid position at a glance
- Serving utilities
- BONNEVILLE POWER ADMINISTRATION, CENTRAL ELECTRIC COOP INC - (OR), CONSUMERS POWER, INC, HOOD RIVER ELECTRIC COOP, NORTHERN WASCO COUNTY PUD, PACIFICORP, PORTLAND GENERAL ELECTRIC CO, PUD NO 1 OF KLICKITAT COUNTY, WASCO ELECTRIC COOP, INC
- ISO / market
- NON_ISO (Not in an organized wholesale market)
- Highest grid access
- 1000 kV
- Substations in county
- 31
- Industrial retail rate
- 8.3¢/kWhState-level EIA-861 industrial average. The map colours by this, not by a per-county rate.
- Per-utility rates in county
- 5 of 9 serving utilities: 6.8 to 9.7¢/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
- None on record
- Proposed generation
- 2,103 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
- 212 lb CO2/MWh
- Water withdrawals
- 82 Mgal/dAll uses, freshwater. Water already withdrawn locally, not water available for a new load.
- Construction labor near site
- 60,930 employed in construction within ~120 km (9 of 11 counties reporting)A 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 Wasco
What follows is a screening-grade read of Wasco, Oregon, built only from named public datasets. Grid access in Wasco extends to 1,000 kV, the extra-high-voltage class. The mapped layer packs 31 substations into Wasco, a dense spread of options.
Sitting outside any organized market, Wasco, Oregon handles interconnection through its utility rather than a central operator. For Wasco, the rate shown is the state industrial average of 8.3 cents per kWh (EIA-861), a state figure and not a county-specific one. Beneath that state average, the utilities serving Wasco that report an industrial rate span 5 of 9 serving utilities: 6.8 to 9.7¢/kWh, shown as context and never as the county rate.
No interconnection-queue project is on record for Wasco, Oregon in the covered feeds, which reflects either genuine quiet or a queue not yet ingested. EIA-860M records 2,103 MW planned or under construction for Wasco. Wasco sits under a balancing authority that eGRID puts at 212.458 lb CO2 per MWh.
Wasco withdrew 82.17 million gallons per day for all uses in the USGS 2015 data, which counts demand, not headroom. About 60,930 people are employed in construction within a 120 km commute of Wasco (BLS QCEW), which frames staffing distance rather than free labour.
For Wasco, treat this as screening-grade county context useful for narrowing a search rather than settling a site. Taken together, the figures for Wasco, Oregon describe the grid around a prospective site, drawn from public data with their gaps left visible on purpose. To move past screening in Wasco, Oregon, a specific address needs its own interconnection study, which this page does not attempt. The figures for Wasco, Oregon refresh as their public datasets do, and the exact sources and dates sit in the source log below this section.