Power by county
King George, VA: data center power outlook
King George, Virginia is served through the PJM market (PJM Interconnection), and the figures below describe the public grid around a prospective data center site there. King George carries 5 mapped substations within its boundary, and the highest reachable grid access is 230 kV. Service in King George spans 3 utilities, with NORTHERN NECK ELEC COOP, INC, RAPPAHANNOCK ELECTRIC COOP, VIRGINIA ELECTRIC & POWER CO among those mapped.
Grid position at a glance
- Serving utilities
- NORTHERN NECK ELEC COOP, INC, RAPPAHANNOCK ELECTRIC COOP, VIRGINIA ELECTRIC & POWER CO
- ISO / market
- PJM (PJM Interconnection)
- Highest grid access
- 230 kV
- Substations in county
- 5
- Industrial retail rate
- 9.4¢/kWhState-level EIA-861 industrial average. The map colours by this, not by a per-county rate.
- Per-utility rates in county
- 2 of 3 serving utilities: 6.0 to 8.8¢/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
- 716 lb CO2/MWh
- Water withdrawals
- 2.7 Mgal/dAll uses, freshwater. Water already withdrawn locally, not water available for a new load.
- Construction labor near site
- 233,591 employed in construction within ~120 km (55 of 58 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 King George
What follows is a screening-grade read of King George, Virginia, built only from named public datasets. At 230 kV, King George sits in the transmission class that a large load would look to. King George, Virginia carries a thin 5-substation footprint in the mapped layer, concentrating where a connection could land.
Interconnection over King George runs through the PJM market (PJM Interconnection) and its rules. For King George, the rate shown is the state industrial average of 9.4 cents per kWh (EIA-861), a state figure and not a county-specific one. Beneath that state average, the utilities serving King George that report an industrial rate span 2 of 3 serving utilities: 6.0 to 8.8¢/kWh, shown as context and never as the county rate.
No interconnection-queue project is on record for King George, Virginia in the covered feeds, which reflects either genuine quiet or a queue not yet ingested. EIA-860M lists nothing planned or under construction for King George, Virginia, which is a national filing and so a real zero. King George sits under a balancing authority that eGRID puts at 716.09 lb CO2 per MWh.
King George withdrew 2.68 million gallons per day for all uses in the USGS 2015 data, which counts demand, not headroom. About 233,591 people are employed in construction within a 120 km commute of King George (BLS QCEW), which frames staffing distance rather than free labour.
For King George, treat this as screening-grade county context useful for narrowing a search rather than settling a site. Taken together, the figures for King George, Virginia describe the grid around a prospective site, drawn from public data with their gaps left visible on purpose. To move past screening in King George, Virginia, a specific address needs its own interconnection study, which this page does not attempt. The figures for King George, Virginia refresh as their public datasets do, and the exact sources and dates sit in the source log below this section.