WELL · 42-071-32394 · DISTRICT 3

Oyster Bayou Field Unit #81

Y

Chambers County · Oyster Bayou field · Producing  · Vertical

Oyster Bayou Field Unit #81 (API 42-071-32394) is a well in Chambers County operated by Denbury Onshore LLC, completed May 5, 2025 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued June 15, 2010, permitted to 8,700 ft.

Completion filings report 4 formation tops, including Anahuac, Heterostegina, Heterostengina, Frio.

Its lease has reported 23.1M barrels of oil and 2.94K mcf of gas since June 2010, last reporting in July 2026. The lease carries 102 wells, so these are lease totals, not this well alone.

Operator of record

Denbury Onshore LLC

Based in
Spring, TX
P-5 status
Active (A)
P-5 last filed
Dec 30, 2025
Permits on file
789
Phone
(866) 831-3235

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDenbury Onshore LLC
Production reportsDenbury Onshore, LLCthrough Apr 2026
Latest permitDenbury Onshore, LLCJun 15, 2010
8,700
total depth, ft
1
permits on file
Jun 15, 2010
last permit issued
May 5, 2025
completed
23.1M
cumulative oil, bbl
2.94K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2010 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 5, 2025
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; they carry 102 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Oyster Bayou Field Unit O-3-25515Oyster BayouDenbury Onshore, LLC10223.1M2.94KJun 2010 – Jul 2026

Oil, barrels lease total

Last 12 months 972,775 · prior 12 1,191,053(-18%)

050K100K150K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Denbury Onshore, LLCJun 2010 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
697404-99DrillDenbury Onshore, LLCJun 10, 2010Jun 15, 2010Jan 29, 20118,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-25515————

Formation tops

As filed on W-2/G-1. Subsea from 6 ft elevation.Download CSV →

FormationMD ftSubsea
Anahuac6,628-6,622
Heterostegina7,220-7,214
Heterostengina7,220-7,214
Frio8,003-7,997

Perforations

Perforated and open-hole intervals.

FromToType
8,1468,150Perforated
8,1568,273Perforated
8,2828,305Perforated
8,3098,343Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,21712.25490 S
9.6251,21812.25490 S
5.58,5758.752,220 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Jul 29, 2025Jun 3, 2025—
00Jun 15, 2023Apr 16, 2023—
00Aug 9, 2018Jul 3, 2018—
00Nov 2, 2015Jun 23, 2015—
00Jan 30, 2013Aug 17, 2012—
00Jul 30, 2012Mar 1, 2012Yes

The source documents

Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.

About this data

Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.

New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease

Developers: this page as JSON is GET /v1/data/wells/07132394, documented in the API reference.