WELL · 42-013-34383 · DISTRICT 1

Peeler Ranch #2H

N

Atascosa County · Eagleville (Eagle Ford-1) field  · Horizontal

Peeler Ranch #2H (API 42-013-34383) is a horizontal well in Atascosa County operated by Dewbre Petroleum Corporation, completed February 18, 2012.

The RRC has issued one drilling permit, issued June 7, 2011, permitted to 10,000 ft.

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

Its 2 leases have reported 179K barrels of oil and 38.9K mcf of gas since December 2010, last reporting in July 2026. The leases carry 3 wells, so these are lease totals, not this well alone.

Operator of record

Dewbre Petroleum Corporation

Based in
Corpus Christ, TX
P-5 status
Active (A)
P-5 last filed
Oct 22, 2025
Permits on file
366
Phone
(361) 888-7978

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDewbre Petroleum Corporation
Production reportsDewbre Petroleum Corporationthrough Apr 2026
Latest permitDewbre Petroleum CorporationJun 7, 2011
10,000
total depth, ft
1
permits on file
Jun 7, 2011
last permit issued
Feb 18, 2012
completed
179K
cumulative oil, bbl
38.9K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 2010 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 18, 2012
Shut in
—
Plugged
—

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 2 leases this well is completed on; they carry 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Peeler Ranch O-1-15472Eagleville (Eagle Ford-1)Dewbre Petroleum Corporation2140K38.1KDec 2010 – Jul 2026
Peeler Ranch B O-1-17494Eagleville (Eagle Ford-1)Dewbre Petroleum Corporation138.4K810Apr 2014 – Jul 2026

Oil, barrels lease total

Last 12 months 2,216 · prior 12 2,669(-17%)

05001K202420252026

Chain of custody

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

  1. 1Dewbre Petroleum CorporationMar 2011 → Apr 2026
  2. 2Wapiti Operating, LLCJan 2012 → Feb 2013
  3. 3Argent Energy (US) Holdings Inc.Mar 2013 → May 2016

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
717730-99DrillDewbre Petroleum CorporationJun 3, 2011Jun 7, 2011Jan 25, 201210,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-15472————
—— O-1-17494————

Formation tops

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

FormationMD ftSubsea
Austin Chalk9,122-8,827
Eagle FordEAGLEFORD9,437-9,142
Buda9,705-9,410

Perforations

Perforated and open-hole intervals.

FromToType
10,03014,849Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6254,41512.25836 S
5.514,9368.51,239 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
00May 12, 2014Mar 13, 2012—
00May 25, 2012Mar 13, 2012—
00Mar 15, 2012Dec 15, 2011Yes

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