Mewbourne Oil Co New Mexico Operator Brief: Eddy And Lea Permit Activity (2026)

Mewbourne Oil Co has 37 New Mexico permit rows and 42 separately screened reported-spud rows in the September 18, 2026 review. Eddy carries more permit records; both Eddy and Lea have reported drilling starts. These are state-record counts, not a rig count or a production ranking.

The screen starts June 20, 2026 and includes records available at retrieval on September 18. Permits are selected by issue date; spuds are selected independently by reported-spud date. A well permitted before this window can therefore appear in the spud count without appearing in the permit count.

Mewbourne Eddy And Lea Permit Activity

All returned rows use the filed label MEWBOURNE OIL CO. The latest matched permit issue date is September 11, 2026; the latest matched spud date is September 1, 2026. Those are dates within this operator screen, not a claim that every New Mexico dataset is complete through those days.

A Mewbourne Record You Can Check

One returned permit row identifies RUNWAY 26 30 FEDERAL COM #557H, API 3001558956, in Eddy County, with an issue date of September 11, 2026. Its reported-spud field was blank in the reviewed response. That blank does not establish that drilling has not started; it means the reviewed row does not supply that date.

Keep the identifier as text when moving it into a spreadsheet or another tool. The permit response exposes the API in an identifier field named api12, even though this New Mexico example contains ten digits. Preserve the returned identifier rather than adding digits to make it match the field name.

For independent source review, start at New Mexico OCD permitting and search the well identifier. Confirm the well name, filed operator, county and document dates before making a commercial decision. The example above was checked in EnergyNetWatch's retained API response; this article does not claim a separate document-by-document reconciliation of every returned row.

How To Get The Mewbourne Permit Table

The API reference describes authenticated access. This request shape was used for the September 18 review:

GET /api/public/permits?state=NM&search=MEWBOURNE&days=90&limit=200&page=1

Run a separate request with spuddedOnly=true to screen by reported-spud date. The first request returned 37 permit rows; the separate request returned 42 spud rows. Both complete result sets fitted on one page. For a later request, inspect pagination.total and continue through every page when necessary; do not assume a first-page sample is the full operator count.

The search parameter matches operator-name text, not a maintained corporate-family identifier. Review every distinct returned label before grouping the results. All labels in these two responses matched MEWBOURNE OIL CO, but that observation does not guarantee future responses will have an identical label set.

The permits endpoint uses six API units per request under the reviewed endpoint definition. These two one-page requests therefore use twelve units. Pagination and additional requests consume more units. See prepaid API pricing and New Mexico coverage before choosing access for a particular workflow. Standard API credits do not require a Premium app subscription.

For a prepared delivery instead, request a Mewbourne Eddy/Lea activity table. Specify the filed label, counties, dates and desired format. Custom preparation and delivery scope are agreed separately from self-service API credits.

Why More Spuds Than Permits Is Not A Conversion Rate

The two columns represent different event cohorts. A permit issued in an earlier month can have a reported spud inside the selected period. A recent permit can still have no reported spud in the loaded record.

Dividing 42 by 37 would not measure permit conversion. To investigate conversion, choose a fixed permit cohort, join its records to subsequent spud evidence using identifiers, define the observation period, and retain unmatched rows. Deduplicate repeated events before reporting a percentage. This page does not perform that cohort analysis.

Nor do these counts prove 42 rigs are active. A spud is a recorded drilling start. It is not a live rig location, completion, first production, equipment order or open supplier contract. Use the counts to choose records for further research, not as a list of guaranteed sales opportunities.

Where Mewbourne Is Active In This Screen

Eddy contains about 68% of the reviewed permit rows. That makes it the larger permit group in this particular window, while Lea remains important for a two-county review. This does not establish Mewbourne's total acreage position, capital allocation or company-wide drilling schedule.

For territory research, keep the county comparison attached to the underlying well identifiers. A county total can help decide where to look first, but a map and record review are needed to distinguish individual locations, nearby wells and historical work. Do not infer a new project simply because several rows share a similar name.

Use the Eddy County permit page and Lea County permit page for broader operator context. Their own dated windows may differ from this review, so their counts should not be added to this table.

Source Dates And The Earlier Snapshot

This replaces the August 8 operator snapshot as the main displayed review. The earlier page showed 41 permits, 32 spuds and 213 trailing-year permits using windows anchored to July state-source dates. The new screen uses a June 20 lower bound calculated from the September 18 retrieval date. We have not refreshed the trailing-year figure here.

Those differences prevent a like-for-like growth calculation. A lower permit count does not, by itself, establish declining activity; changes in the selected period, reporting and loaded records can all affect the result. A valid trend comparison needs equivalent adjacent periods and a consistent source basis.

The source dates also answer different questions. Issue date describes the permit event. Reported-spud date describes a drilling-start record. Retrieval time describes when we inspected the available data. None is a promise that reporting is complete or that later amendments will leave the count unchanged.

What To Keep In A Mewbourne Export

Keep API identifier, filed operator, county, issue date and reported-spud date together. Retain the request filters and retrieval date beside the exported file. Keep blank dates blank rather than replacing them with zero, the permit date or today's date.

A useful review table also records why a row was included: permit-date selection, spud-date selection or both. That allows a colleague to distinguish the two cohorts without reconstructing the original requests. If combining the two responses into one well list, deduplicate using the appropriate record identity and preserve both event dates.

Infrastructure and production require separate evidence. This brief does not establish Mewbourne ownership of a gathering line, facility construction or produced volumes. Check operator identity and source coverage in those datasets before attaching them to the same account view.

What To Watch Next

Watch for later permit dates, newly reported spuds and changes in the Eddy/Lea distribution using the same selection method. Preserve this dated snapshot before updating the next one. An unchanged latest date can reflect source reporting or availability, not necessarily a pause in field activity.

For recurring work, repeat the bounded requests, retain both responses and compare identifiers and dates rather than only totals. Review new names or county discrepancies explicitly. A prepared table can include that review, but its scope should be stated before delivery.

Frequently Asked Questions

What operator label is used for this Mewbourne brief?

MEWBOURNE OIL CO, exactly as returned by the reviewed New Mexico records. This is not an all-affiliate corporate rollup.

Is this a production ranking?

No. Permit and reported-spud records are separate from production volumes, reserves and company financial results.

Why does Eddy County matter more in this pull?

Eddy has 25 permit rows compared with Lea's 12 in the reviewed window. That is a permit-count comparison, not a comparison of acreage or spend.

Why include Lea County if Eddy leads?

Lea has 12 permit rows and 15 independently selected spud rows. Excluding it would omit part of the reviewed operator activity.

What does EnergyNetWatch add beyond the public table?

The API supplies repeatable filtered records with identifiers and dates. Prepared tables are a separate option when a team needs a reviewed delivery. Available fields and history depend on coverage.

How current are the Mewbourne counts on this page?

Reviewed September 18, 2026, with a June 20 lower date bound. Latest matched permit: September 11. Latest matched spud: September 1. Later responses can differ.

For broader scope or delivery questions, request EnergyNetWatch access.