North Dakota Bakken Operator Activity Watchlist: June 2026 Review

Correction — September 12, 2026: The original June review described 1,183 May records and a 60.1% increase as drilling-permit activity. Those permit-issuance claims are withdrawn. The North Dakota well-index loader stores a well-status date in the field called issue_date. The original historical cohort has not been independently reconstructed as issued permits. This page retains its original address and publication date; the interpretation below replaces the unsupported permit-growth claims.

What the North Dakota dates tell you

A recent date does not necessarily identify a new well or a newly issued drilling permit. In the reviewed North Dakota well-index feed, WellStatusDate describes the source's well-status date. The loader carries that value into issue_date, which can make older wells appear in a recent-date API search.

The September 12 check matched ten database examples to retained source rows. One Williams County well had a January 1957 spud date and a September 2026 well-status date. A McKenzie County example had a January 1991 spud date and a September 2026 well-status date. Neither status date establishes new permit issuance.

A county/operator list can support research into existing wells and reported status. It cannot support a new-permit growth claim without separate issuance evidence.

Choose the event before building an operator list

For permits issued each day, North Dakota DMR directs readers to its Daily Activity Reports. Its well-permitting guidance also identifies the monthly publication as a source for monthly permit statistics. These answer a different question from a well-index status-date filter.

McKenzie and Williams county research

Start with the county, source-filed operator label and well/file identifier. Preserve identifiers as text and retain the date field used for selection. A full operator table should state whether it groups issued permits, wells, or records selected by status date.

Do not call a status-window operator share a permit share. Do not infer a purchasing budget or service award from either count. For a territory review, identify the relevant event, then inspect the well location and source records before choosing accounts.

The checked county cohorts had distinct well/file identifiers, so duplicate rows did not explain their large recent-date totals. That does not turn those totals into newly issued permits.

Using the API responsibly

For North Dakota rows from this source, treat stored issue_date as a well-status date, not a verified permit date. Keep the requested lookback, retrieval date and source date in an export. Finish pagination before making statements about the full selected cohort.

Ask an AI assistant to group supplied records by exact operator label, state the event/date basis, flag missing evidence and avoid inferring new permitting from recent status dates. A field name alone is not enough to classify the event.

See why source dates differ and North Dakota coverage. Dataset coverage does not mean every date represents the same event.

Request a North Dakota research scope

Need a reviewed county/operator table? Request a North Dakota research scope. Specify the county, time window and whether you need permit issuance, well status or production. Available fields and delivery are agreed before purchase; verified new-permit counts are not promised from the status-date feed.

For repeated extraction, review API access and pricing. Confirm that the available fields answer your question before buying a larger extraction.

Frequently asked questions

Does this correction mean the wells are missing?

No. The checked records exist. The issue is the meaning of the date used to select and describe them.

Are the original May permit-growth figures still valid?

They are not verified as permit-issuance figures and should not be reused as such. This correction does not claim a new reconstruction of the June historical dataset.

Does a recent status date mean drilling just started?

No. Check a reported spud date separately. The raw-source examples include wells drilled decades before their recent status dates.

Where should I start for a county watchlist?

Define the event, retain its source and date, then group by county and operator. Continue with the North Dakota state watchlist, but verify event definitions before using aggregates as new-permit counts.

Sources and review boundaries

• EnergyNetWatch read-only database and retained North Dakota well-index comparison, September 12, 2026; source file retrieved September 7.
• North Dakota DMR Daily Activity Reports and well-permitting guidance linked above.
• Original publication June 21, 2026. The September correction addresses its permit interpretation; it is not a fresh production report or complete statewide permit audit.