What North Dakota oil and gas data does EnergyNetWatch cover?
The current listed datasets are Wells, Production coverage, Permits/API support where available, Coverage comparison. Coverage depth and source timing vary by record family.
North Dakota is live in the app state set and remains a major Bakken coverage focus because it materially improves oil and gas coverage.
The coverage table summarizes state availability and dataset parity. State sources publish different record types on different schedules, so permit coverage, production coverage, and workflow depth are listed separately. Read the coverage methodology.
This page explains source coverage and caveats. The Data Explorer shows a lagged public monthly snapshot for state, county, and operator lookup.
North Dakota is a major Bakken state and a material part of the multi-state coverage story.
| Status | Full |
|---|---|
| Permits | Live |
| Production | Live |
| Coverage parity | Permits + production |
Refresh cadence is shown by workflow as validation hardens.
The current North Dakota coverage page lists each dataset separately so production, permits, wells, maps, and other records are not presented as if they have identical depth or timing.
These are the current workflows supported by the listed North Dakota source coverage. The record type and latest available source date should stay visible when results move into a map, export, report, alert, or API integration.
Use this page to confirm which North Dakota record families are represented and where the source caveats apply.
Open the North Dakota data snapshot for lagged monthly trends, county context, and masked sample records.
See the oil and gas data use cases for operator monitoring, territory planning, sales intelligence, maps, exports, and alerts.
Review the commercial oil and gas data API when the supported North Dakota records need to feed a dashboard, CRM, monitor, or internal application.
The current listed datasets are Wells, Production coverage, Permits/API support where available, Coverage comparison. Coverage depth and source timing vary by record family.
Refresh cadence is shown by workflow as validation hardens. Permit-oriented coverage with ongoing production and workflow-depth monitoring.
API availability depends on the dataset, account, endpoint family, and current state coverage. The commercial API page and public reference describe the supported integration path.