Power by county
Jefferson, WA: data center power outlook
Jefferson, Washington 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. Jefferson carries 20 mapped substations within its boundary, and the highest reachable grid access is 230 kV. Service in Jefferson spans 7 utilities, with BONNEVILLE POWER ADMINISTRATION, PUD NO 1 OF CLALLAM COUNTY, PUD NO 1 OF GRAYS HARBOR COUNTY among those mapped.
Grid position at a glance
- Serving utilities
- BONNEVILLE POWER ADMINISTRATION, PUD NO 1 OF CLALLAM COUNTY, PUD NO 1 OF GRAYS HARBOR COUNTY, PUD NO 1 OF JEFFERSON COUNTY, PUD NO 1 OF MASON COUNTY, PUD NO 3 OF MASON COUNTY, PUGET SOUND ENERGY INC
- ISO / market
- NON_ISO (Not in an organized wholesale market)
- Highest grid access
- 230 kV
- Substations in county
- 20
- Industrial retail rate
- 6.9¢/kWhState-level EIA-861 industrial average. The map colours by this, not by a per-county rate.
- Per-utility rates in county
- 6 of 7 serving utilities: 1.3 to 7.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
- None on file (EIA-860M)Units 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
- 4.2 Mgal/dAll uses, freshwater. Water already withdrawn locally, not water available for a new load.
- Construction labor near site
- 16,930 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 Jefferson
What follows is a screening-grade read of Jefferson, Washington, built only from named public datasets. At 230 kV, Jefferson sits in the transmission class that a large load would look to. The mapped layer places 20 substations across Jefferson, a moderate density.
Jefferson, Washington is not inside an organized market, which leaves interconnection to the utility and bilateral contracts. For Jefferson, the rate shown is the state industrial average of 6.9 cents per kWh (EIA-861), a state figure and not a county-specific one. Beneath that state average, the utilities serving Jefferson that report an industrial rate span 6 of 7 serving utilities: 1.3 to 7.7¢/kWh, shown as context and never as the county rate.
No interconnection-queue project is on record for Jefferson, Washington in the covered feeds, which reflects either genuine quiet or a queue not yet ingested. Jefferson, Washington has no EIA-860M generation on file, which reads as zero rather than as a gap. Jefferson sits under a balancing authority that eGRID puts at 212.458 lb CO2 per MWh.
Jefferson withdrew 4.16 million gallons per day for all uses in the USGS 2015 data, which counts demand, not headroom. About 16,930 people are employed in construction within a 120 km commute of Jefferson (BLS QCEW), which frames staffing distance rather than free labour.
For Jefferson, treat this as screening-grade county context useful for narrowing a search rather than settling a site. Taken together, the figures for Jefferson, Washington describe the grid around a prospective site, drawn from public data with their gaps left visible on purpose. To move past screening in Jefferson, Washington, a specific address needs its own interconnection study, which this page does not attempt. The figures for Jefferson, Washington refresh as their public datasets do, and the exact sources and dates sit in the source log below this section.