TEXAS · WELLS · GONZALES COUNTY · ADELE DUBOSE LEASE · API 42-177-32685 · DISTRICT 01

Adele Dubose #4

On schedule

Gonzales County · Eagleville (Eagle Ford-1) field · Producing  · Horizontal

Adele Dubose #4 (API 42-177-32685) is a horizontal well in Gonzales County operated by Verdun Oil & Gas LLC, completed July 16, 2013 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued September 11, 2012, permitted to 11,766 ft.

It was permitted by Rosetta Resources Operating LP and has since transferred to Verdun Oil & Gas LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Austin Chalk, Eagle Ford, Anacacho.

Its lease has reported 4.84M barrels of oil and 12.6M mcf of gas since February 2012, last reporting volume in April 2026. The lease carries 16 wells, so these are lease totals, not this well alone.

Operator of record

Verdun Oil & Gas LLC

Permitted by Rosetta Resources Operating LP; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Oct 22, 2025
Permits on file
400
Phone
(713) 337-9300

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleVerdun Oil & Gas LLC
Production reportsVerdun Oil & Gas LLCthrough Apr 2026
Latest permitRosetta Resources Operating LPSep 11, 2012

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

11,766
total depth, ft
1
permits on file
Sep 11, 2012
last permit issued
Jul 16, 2013
completed
4.84M
cumulative oil, bbl
12.6M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2012 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 16, 2013
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active – Extension (X)

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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

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 16 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Adele Dubose O-1-15914Eagleville (Eagle Ford-1)Verdun Oil & Gas LLC164.84M12.6MFeb 2012 – Apr 2026

Oil, barrels lease total

Last 12 months 183,532 · prior 12 265,330(-31%)

020K40K202420252026

Gas, mcf lease total

Last 12 months 775,109 · prior 12 947,510(-18%)

050K100K150K202420252026

Wells named Adele Dubose

Verdun Oil & Gas LLC's other wells filed under this lease name in Gonzales County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Chain of custody

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

  1. 1Rosetta Resources Operating LPFeb 2012 → May 2017
  2. 2Verdun Oil & Gas LLCJun 2017 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
747353-99DrillRosetta Resources Operating LPAug 29, 2012Sep 11, 2012Nov 2, 201211,800

Completions

CompletedLeaseFieldOperatorStatusDepth
Jul 16, 2013Adele Dubose O-1-15914Eagleville (Eagle Ford-1)Verdun Oil & Gas LLCProducing11,766

Formation tops

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

FormationMD ftSubsea
Austin Chalk11,110-10,821
Eagle Ford11,700-11,411
Eagle FordEAGLEFORD11,700-11,411
Anacacho——

Perforations

Perforated and open-hole intervals.

FromToType
12,28718,488Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6253,60012.251,105 S
5.518,5908.753,370 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Apr 23, 2014Apr 16, 2014—
00Oct 21, 2013Aug 21, 2013Yes

Well logs

1 log loaded from the RRC's log index, the latest received Nov 12, 2015. Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
RESISTIVITYSpans Austin Chalk, Eagle FordTIFF11,150 to 18,628Nov 12, 2015run Nov 17, 20122.66

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it.

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/17732685, documented in the API reference.