Power by county
Bertie, NC: data center power outlook
Bertie, North Carolina is served through the PJM market (PJM Interconnection), and the figures below describe the public grid around a prospective data center site there. Bertie carries 8 mapped substations within its boundary, and the highest reachable grid access is 230 kV. Service in Bertie spans 9 utilities, with DUKE ENERGY PROGRESS - (NC), EDGECOMBE-MARTIN COUNTY E M C, HALIFAX ELECTRIC MEMBER CORP among those mapped.
Grid position at a glance
- Serving utilities
- DUKE ENERGY PROGRESS - (NC), EDGECOMBE-MARTIN COUNTY E M C, HALIFAX ELECTRIC MEMBER CORP, MECKLENBURG ELECTRIC COOPERATIVE, ROANOKE ELECTRIC MEMBER CORP, TIDELAND ELECTRIC MEMBER CORP, TOWN OF HAMILTON - (NC), TOWN OF WINDSOR- (NC), VIRGINIA ELECTRIC & POWER CO
- ISO / market
- PJM (PJM Interconnection)
- Highest grid access
- 230 kV
- Substations in county
- 8
- Industrial retail rate
- 7.8¢/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: 7.9 to 11.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
- None on record
- Proposed generation
- 4 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
- 716 lb CO2/MWh
- Water withdrawals
- 7.3 Mgal/dAll uses, freshwater. Water already withdrawn locally, not water available for a new load.
- Construction labor near site
- 51,910 employed in construction within ~120 km (38 of 40 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 Bertie
What follows is a screening-grade read of Bertie, North Carolina, built only from named public datasets. At 230 kV, Bertie sits in the transmission class that a large load would look to. The mapped layer places 8 substations across Bertie, a moderate density.
Interconnection over Bertie runs through the PJM market (PJM Interconnection) and its rules. For Bertie, the rate shown is the state industrial average of 7.8 cents per kWh (EIA-861), a state figure and not a county-specific one. Beneath that state average, the utilities serving Bertie that report an industrial rate span 5 of 9 serving utilities: 7.9 to 11.0¢/kWh, shown as context and never as the county rate.
Across the covered feeds, Bertie, North Carolina carries no interconnection-queue project, from either real quiet or a feed not yet loaded. EIA-860M records 3.9 MW planned or under construction for Bertie. Bertie sits under a balancing authority that eGRID puts at 716.09 lb CO2 per MWh.
Bertie withdrew 7.26 million gallons per day for all uses in the USGS 2015 data, which counts demand, not headroom. About 51,910 people are employed in construction within a 120 km commute of Bertie (BLS QCEW), which frames staffing distance rather than free labour.
For Bertie, treat this as screening-grade county context useful for narrowing a search rather than settling a site. Taken together, the figures for Bertie, North Carolina describe the grid around a prospective site, drawn from public data with their gaps left visible on purpose. To move past screening in Bertie, North Carolina, a specific address needs its own interconnection study, which this page does not attempt. The figures for Bertie, North Carolina refresh as their public datasets do, and the exact sources and dates sit in the source log below this section.