What New Mexico oil and gas data does EnergyNetWatch cover?
The current listed datasets are Wells, Production, Permits/completions context, Maps, FracFocus completions. Coverage depth and source timing vary by record family.
New Mexico is a high-value launch state for Permian operator, well, permit, and production monitoring.
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.
Second-largest oil state in the documented 2024 production coverage model.
| Status | Full |
|---|---|
| Permits | Live |
| Production | Live |
| Coverage parity | Permits + production |
Refresh cadence depends on source availability and automation maturity.
The current New Mexico 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 New Mexico 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 New Mexico record families are represented and where the source caveats apply.
Open the New Mexico 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 New Mexico records need to feed a dashboard, CRM, monitor, or internal application.
The current listed datasets are Wells, Production, Permits/completions context, Maps, FracFocus completions. Coverage depth and source timing vary by record family.
Refresh cadence depends on source availability and automation maturity. Strong recurring refresh with state-source dependent production and permit timing.
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.