How to Access Free Oil & Gas Production Data Across 26 States (2026 Guide)
Learn where free oil and gas production data comes from, why state records are fragmented, and how EnergyNetWatch tracks 26 states.
By Johnathan · Reviewed by EnergyNetWatch Research · Last updated 2026-05-04
Key Takeaways
- EnergyNetWatch tracks a 26-state public oil and gas data landscape across production, permits, and source parity.
- Public samples for Texas, New Mexico, and North Dakota use real records that are rounded, masked, selected, and intentionally lagged.
- State portals are useful for source verification; normalized app workflows are useful when the work becomes recurring, multi-state, or export-heavy.
Oil and gas production data is public in the United States, but public does not mean easy to use.
Every producing state publishes records through its own regulatory systems. Texas has Railroad Commission production queries and downloads. New Mexico has OCD source data. North Dakota has its own state source structure. Other states use RBDMS-related systems, web portals, CSV files, spreadsheets, maps, PDF reports, or source-specific downloads.
The result is predictable: the data exists, but comparing wells, operators, counties, and states requires source knowledge, normalization, and refresh tracking. A single state portal can answer a narrow lookup question. It usually cannot support repeatable multi-state production analysis, operator monitoring, permit-to-production workflows, maps, exports, and internal reporting without additional work.
EnergyNetWatch tracks the public oil and gas data landscape across 26 states. The public site includes a state coverage table and selected public data samples for Texas, New Mexico, and North Dakota. Those samples use real EnergyNetWatch records that are rounded, masked, selected, and intentionally lagged for display.
Start with the state coverage table, then review the public data samples for state-level examples.
Free Oil and Gas Production Data by State
Oil and gas data starts with state regulatory reporting. Operators file production, permit, completion, status, and well records with state agencies. Those records are commonly public, but the access pattern changes by state.
That state-by-state variation is the core problem.
One state may provide a web query. Another may provide CSV downloads. Another may publish interactive maps. Another may expose data through RBDMS-related systems. Some sources are easy for one-off lookup but difficult for repeatable bulk analysis. Others provide bulk data but require source-specific parsing and joins.
EnergyNetWatch tracks public coverage across 26 states, but coverage parity is not identical everywhere. A state may have live permit coverage, live production coverage, both, or a pending/deferred source workflow.
| State | Code | Public coverage status | Public parity read |
|---|---|---|---|
| Texas | TX | Full | Permits + production |
| New Mexico | NM | Full | Permits + production |
| Louisiana | LA | Full | Permits + production |
| New York | NY | Full | Permits + production |
| Colorado | CO | Full | Permits + production |
| West Virginia | WV | Full | Permits + production |
| Wyoming | WY | Full | Permits + production |
| Utah | UT | Full | Permits + production |
| Alaska | AK | Full | Production coverage |
| Ohio | OH | Full | Permits + production |
| North Dakota | ND | Full | Permits + production |
| Pennsylvania | PA | Full | Permits + production |
| California | CA | Full | Permits + production |
| Montana | MT | Full | Permit automation; production pending |
| Kansas | KS | Full | Permit automation; production pending |
| Arkansas | AR | Full | Permit automation; production pending |
| Mississippi | MS | Full | Production coverage; permits pending |
| Illinois | IL | Permits only | Permit automation only |
| Michigan | MI | Permits only | Permit automation only |
| Alabama | AL | Permits only | Permit automation only |
| Kentucky | KY | Permits only | Permit automation only |
| Nebraska | NE | Permits only | Permit automation only |
| Florida | FL | Permits only | Permit automation only |
| South Dakota | SD | Permits only | Permit automation only |
| Oklahoma | OK | Deferred | Permit coverage; production deferred |
| Indiana | IN | Pending | Pending source automation |
The purpose of the table is not to claim every state has the same depth. It is to make the differences visible. Production, permits, maps, exports, and workflow depth are separate questions.
EnergyNetWatch Public Data Samples
EnergyNetWatch publishes selected public samples so buyers and researchers can inspect coverage, source handling, and workflow fit before requesting app access.
Current public samples:
| State | Public sample | Why it is included |
|---|---|---|
| Texas | Texas data sample | Largest core sample; important for Permian, Eagle Ford, Haynesville, and Barnett workflows |
| New Mexico | New Mexico data sample | Strong Delaware Basin and San Juan Basin comparison point |
| North Dakota | North Dakota data sample | Bakken and Williston Basin sample outside the Permian |
These samples are based on real EnergyNetWatch records. Public values are rounded, masked, selected, and intentionally lagged. The public site shows enough to evaluate data quality and source handling without publishing the full app dataset.
Current public sample data:
| State | Latest public production month | Public lag | Public sample focus | Example public values |
|---|---|---|---|---|
| Texas | 2026-02 | 3 months | Permian, Eagle Ford, Haynesville, Barnett | 724K+ indexed well records; 3.6M+ monthly production records |
| New Mexico | 2026-02 | 3 months | Delaware Basin, San Juan Basin | 195K+ indexed well rows; Lea, Eddy, San Juan, and Rio Arriba county context |
| North Dakota | 2026-02 | 3 months | Bakken, Williston Basin | McKenzie, Mountrail, Williams, and Dunn county context |
Rounded six-month public trend examples:
| State | Sep 2025 oil | Feb 2026 oil | Sep 2025 gas | Feb 2026 gas |
|---|---|---|---|---|
| Texas | 178M bbl | 186M bbl | 1040B mcf | 1088B mcf |
| New Mexico | 58M bbl | 63M bbl | 265B mcf | 279B mcf |
| North Dakota | 39M bbl | 43M bbl | 116B mcf | 125B mcf |
The values are intentionally summarized. The point is to show the shape of the data, not to turn the public site into a bulk export.
Why Free Oil and Gas Data Is Still Hard To Use
The common issue is not whether public data exists. It is whether the data is usable for repeatable analysis.
Common problems include:
- Source lag: production data often trails current operations by one to three months, and some reports are revised later.
- Different schemas: each state has its own field names, files, query systems, and source logic.
- Identifier issues: API numbers, lease numbers, operator IDs, permit numbers, and GIS keys do not always line up cleanly.
- Lease vs well nuance: Texas oil production reporting can require lease-level interpretation.
- Separate source systems: production, permits, completions, status, and GIS may live in different places.
- Limited exports: some public portals are good for lookup but poor for repeatable analysis.
This is why EnergyNetWatch separates coverage, methodology, and public data samples instead of implying that every state is identical.
What a Modern Oil and Gas Data Platform Adds
A modern data platform does not make public data real. The data is already real. The platform makes it searchable, connected, current where available, and usable.
EnergyNetWatch app workflows add:
- current source refreshes where supported
- well-level records and histories
- operator normalization
- permit-to-production context
- maps and coordinates
- exports
- saved workflows
- alerts
- decline curve analysis
- economics
- source caveats
The public Data Explorer shows lagged samples. App access is for current records and full workflows.
How To Use Public Data Before Requesting Access
If you only need source documentation, start with the state portal. If you need to verify a single permit, read a state form, or check a known well, the official source should be part of the process.
If the workflow repeats, the economics change. A recurring operator review, county production monitor, basin comparison, or permit-to-production report can quickly become a manual pipeline. Someone has to download files, parse fields, join identifiers, reconcile operators, manage source changes, and explain freshness.
That is where normalized data becomes useful. The value is not secrecy. The value is making public records searchable, connected, and reliable enough for repeated work.
Frequently Asked Questions
Is oil and gas production data free?
Yes. In the United States, oil and gas production data is generally public regulatory data. The access method, structure, and export quality vary by state.
Why does free oil and gas production data still cost money to use?
The data may be free, but normalization is work. Teams pay for source ingestion, schema handling, joins, operator cleanup, maps, exports, alerts, and workflow tools.
What states does EnergyNetWatch cover publicly?
EnergyNetWatch tracks a 26-state public data landscape and publishes selected lagged samples for Texas, New Mexico, and North Dakota. See the coverage table for current public parity notes.
Are the public sample numbers real?
Yes. Public sample values are based on real EnergyNetWatch records. They are rounded, masked, selected, and intentionally lagged for public display.
When should I use app access instead of public portals?
Use app access when you need current records where available, complete histories, unmasked well records, maps, exports, alerts, decline curve analysis, economics, or saved workflows.
Sources
Data notes
Public EnergyNetWatch examples use real records that are rounded, masked, selected, and intentionally lagged for display. Full current records, exact identifiers, exports, maps, alerts, DCA, economics, and saved workflows are available with app access. Source coverage varies by state; see the coverage table.
Recommended next reads
Texas Oil and Gas Production Data: RRC Records and Public Samples (2026)
Understand Texas oil and gas production data, RRC reporting limits, public sample trends, and when normalized app workflows help.
New Mexico Oil and Gas Production Data: OCD Sources and Public Samples (2026)
Learn how New Mexico oil and gas production data works, where OCD sources fit, and how public EnergyNetWatch samples show Permian context.
Public vs Paid Oil and Gas Data: When State Portals Are Enough (2026)
Compare public vs paid oil and gas data, including state portals, normalized workflows, app access, exports, maps, and public samples.
Why Oil and Gas Data Is Hard to Normalize Across States (2026)
See why oil and gas data normalization is difficult across states, source schemas, identifiers, reporting cadence, permits, and production.
Related EnergyNetWatch pages
Need current records behind this analysis?
Request access for current source refreshes, unmasked well histories, maps, exports, alerts, DCA, economics, and operator workflows.
Request current data access