Devon Q1 2026 Brief: Coterra Merger, New Mexico Lease, and State-Source Activity
Devon/Coterra operator intelligence brief covering New Mexico permit-spud follow-through, lease context, and merger label review.
By Johnathan · Reviewed by EnergyNetWatch Research · Last updated 2026-06-23
Quarterly/event snapshot
This page is a historical source-record snapshot tied to a specific company update or activity event. It links back into durable operator and state workflows.
Key Takeaways
- Devon-linked New Mexico records show 69 trailing-90-day permits and 8 reported spuds in the reviewed records.
- Coterra-linked New Mexico records show 25 trailing-90-day permits and 7 reported spuds in the same source-record review.
- Lea and Eddy should stay as the first county screens instead of turning the page into a broad merger recap.
EnergyNetWatch reviewed Devon and Coterra-linked New Mexico source records in May 2026.
This page is the Q1 2026 event snapshot tied to the merger and lease update.
For the current ongoing workflow, use the durable Devon & Coterra operator intelligence. This page remains the dated company-event layer.
Operator Signal
| Field | Current signal |
|---|---|
| Signal grade | Active watchlist |
| Primary source-record use case | New Mexico permit/spud follow-through after the Devon/Coterra merger and lease activity |
| Company-reported Q1 production | 833,000 Boe/d |
| Company-reported oil | 387,000 bbl/d |
| Devon New Mexico permit signal | 69 trailing-90D permits |
| Devon New Mexico reported-spud signal | 8 reported spuds |
| Coterra New Mexico permit signal | 25 trailing-90D permits |
| Coterra New Mexico reported-spud signal | 7 reported spuds |
| First follow-up | New Mexico Devon/Coterra permit-spud table, then Lea/Eddy lease context |
The company story is merger and acreage. The EnergyNetWatch signal is narrower: which New Mexico source records show follow-up activity, and which labels need to stay visible.
At A Glance
| Field | Current signal |
|---|---|
| Devon Q1 production | 833,000 Boe/d |
| Devon Q1 oil | 387,000 bbl/d |
| Devon Q1 free cash flow | $816M |
| Merger close | Devon and Coterra completed the merger on May 7, 2026 |
| Lease/acquisition context | Devon announced 16,300 net undeveloped acres in Lea and Eddy counties |
| Devon NM permits | 69 trailing-90D permits |
| Devon NM reported spuds | 8 |
| Coterra NM permits | 25 trailing-90D permits |
| Coterra NM reported spuds | 7 |

EnergyNetWatch public snapshot for Devon and Coterra New Mexico permit and reported-spud activity. Public articles use selected, reviewed examples; authenticated workflows support current source tables, maps, exports, alerts, and API delivery.
What Changed Recently
| Signal | Current signal |
|---|---|
| Company update | Devon reported Q1 results, completed the Coterra merger after quarter-end, and announced a New Mexico Delaware Basin acreage addition. |
| Source-record focus | New Mexico permits and reported spuds are the cleanest public follow-up layer in this brief. |
| Devon activity | 69 trailing-90D New Mexico permits and 8 reported spuds in the reviewed records. |
| Coterra activity | 25 trailing-90D New Mexico permits and 7 reported spuds in the reviewed records. |
| Geography | Lea and Eddy are the first counties to inspect because they connect the lease story to source records. |
New Mexico permits and reported spuds show whether activity followed the merger and lease events in public records.
Source-Record Snapshot
| Field | Current signal |
|---|---|
| Devon New Mexico 90D permits | 69 |
| Devon New Mexico reported spuds | 8 |
| Coterra New Mexico 90D permits | 25 |
| Coterra New Mexico reported spuds | 7 |
| County focus | Lea and Eddy |
| Related state-source layer | North Dakota modeled production context for Devon |
| Source caveat | Devon, Coterra, lease, and acquired-label records should stay separated until reviewed |
This is a source-record activity brief, not a pro forma company-production reconciliation.
Why It Matters
| Business question | EnergyNetWatch signal |
|---|---|
| Did the company story create a source-record follow-up? | Yes. New Mexico permit/spud records give a concrete follow-up path. |
| Where should a commercial user look first? | Lea and Eddy county rows tied to Devon and Coterra labels. |
| What can go wrong in a public-record screen? | Searching only the parent-company name can miss merger, lease, or acquired-label rows. |
| What artifact is useful? | A reviewed New Mexico operator/lease permit-spud table. |
Infrastructure And Midstream Signals
| Layer | Public page treatment | App follow-up |
|---|---|---|
| New Mexico facility / midstream records | Not expanded in this public event brief. | Review operator-linked facility, surface, gathering, and gas-waste rows by Devon/Coterra label before making a project claim. |
| Why limited here | The page focuses on the merger, lease context, permits, and reported spuds without publishing a current lead table. | Request the current Devon/Coterra package with source labels, maps, exports, alerts, and API fields. |
What To Watch Next
| Watch item | Current signal |
|---|---|
| Devon permits | Watch whether trailing-90D permit activity continues into later source refreshes. |
| Coterra labels | Keep Coterra rows visible until the merger label handling is source-confirmed. |
| Reported spuds | Monitor whether permits are followed by drilling-start evidence. |
| Lease geography | Keep Lea and Eddy source rows separate instead of writing a broad Delaware Basin claim. |
| North Dakota context | Treat ND production as a separate state-source layer, not a New Mexico activity signal. |
What To Request
The requestable table is:
Request the current Devon/Coterra New Mexico permit, reported-spud, and lease-context table.
The export should include operator label, county, issue date, reported-spud date, source date, lease context, well records, maps, alerts, and API delivery options.
For the current Devon/Coterra workflow rather than the Q1 event snapshot, use the durable Devon & Coterra operator intelligence page first.
Frequently Asked Questions
What did Devon report for Q1 2026?
Devon reported 833,000 Boe/d of Q1 2026 production, including 387,000 bbl/d of oil, and $816M of free cash flow.
Why does this brief include Coterra?
Devon and Coterra completed their merger on May 7, 2026. Public source labels may not normalize immediately, so Coterra rows remain useful for follow-up.
Why focus on New Mexico?
The public source-record activity in this brief is centered on New Mexico permits and reported spuds, with Lea and Eddy as the first county screens.
Is this the same as Devon's company-reported production?
No. Company figures describe corporate quarterly performance. EnergyNetWatch source records support operator, county, permit, well, and production-month review.
Sources
Data notes
Company-reported figures are from Devon Q1 2026 materials, the Devon/Coterra merger release, and Devon’s New Mexico lease acquisition release. EnergyNetWatch figures are reviewed public state-source snapshots from May 2026 for New Mexico permits/spuds and March 2026 North Dakota modeled production.
Recommended next pages
Devon & Coterra Operator Intelligence: New Mexico Permits, Spuds & Lease Context
Track Devon and Coterra New Mexico activity signals using public permits, reported spuds, lease context, source labels, and Lea/Eddy county records.
New Mexico Drilling Activity Snapshot: Permits and Reported Spuds by Operator
New Mexico operators ranked by trailing 90-day permit records and independent reported spud records from EnergyNetWatch app data.
New Mexico Oil and Gas Production Data: OCD Records, Permits & Spuds
New Mexico OCD production data guide covering wells, operators, counties, permits, reported spuds, source dates, and current table access.
North Dakota Operator Production: March 2026 Oil And Gas Snapshot
EnergyNetWatch reviewed modeled North Dakota well production for March 2026, ranking top Bakken operators by oil and gas volumes while excluding partial April rows.
Related EnergyNetWatch pages
Want the current table behind this analysis?
Public articles use selected examples. Request access if your team needs current source refreshes, exact identifiers, maps, exports, alerts, saved workflows, or API access for this market.
