WELL · 42-127-38765 · DISTRICT 1

Comanche #9982H

Y

Dimmit County · Lorenzo (Austin Chalk) field · Producing  · Horizontal

Comanche #9982H (API 42-127-38765) is a horizontal well in Dimmit County operated by El Toro Resources LLC, completed June 28, 2023 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued April 24, 2023, permitted to 4,800 ft.

Completion filings report 10 formation tops, including Escondido, Olmos, San Miguel, Anacacho.

Its lease has reported 1.55M barrels of oil and 1.16M mcf of gas since May 2016, last reporting in July 2026. The lease carries 38 wells, so these are lease totals, not this well alone.

Operator of record

EL Toro Resources LLC

Oklahoma City, OK · P-5 Y, filed Nov 4, 2025 · 114 permits on file · (432) 238-0069

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEL Toro Resources LLC
Production reportsEL Toro Resources LLCthrough Apr 2026
Latest permitEL Toro Resources LLCApr 24, 2023
4,800
total depth, ft
1
permits on file
Apr 24, 2023
last permit issued
Jun 28, 2023
completed
1.55M
cumulative oil, bbl
1.16M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2016 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jun 28, 2023
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

28.607749, -100.061463

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Dimmit County.

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Comanche O-1-19142Lorenzo (Austin Chalk)EL Toro Resources LLC381.55M1.16MMay 2016 – Jul 2026

Oil, barrels lease total

Last 12 months 284,152 · prior 12 199,858(+42%)

050K100K202420252026

Gas, mcf lease total

Last 12 months 282,230 · prior 12 306,578(-8%)

020K40K60K202420252026

Chain of custody

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

  1. 1EL Toro Resources LLCMay 2016 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
889951-99DrillEL Toro Resources LLCApr 20, 2023Apr 24, 2023May 25, 20234,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-19142————

Formation tops

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

FormationMD ftSubsea
EscondidoESCONDIDO - DISPOSAL789-104
OlmosOLMOS - DISPOSAL1,742-1,057
San MiguelSAN MIGUEL - H2S2,416-1,731
Anacacho3,500-2,815
Austin ChalkAUSTIN CHALK - H2S3,772-3,087
Eagle FordEAGLE FORD - H2S——
EdwardsEDWARDS - H2S——
GeorgetownGEORGETOWN - H2S——
Glen RoseGLEN ROSE - DISPOSAL——
Pearsall——

Perforations

Perforated and open-hole intervals.

FromToType
4,80011,061Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62552212.25288 S
5.511,1058.751,888 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
00Dec 8, 2023Oct 31, 2023Yes

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.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Comanche42-127-38817

0.0 KM · EL Toro Resources LLC · Section with this well →

Escondido810-125
Olmos1,743-1,058
San Miguel2,422-1,737
Austin Chalk3,851-3,166
Eagle Ford4,775-4,090
Pearsall—
Edwards—
Georgetown—

9 TOPS · FIRST 8

Comanche42-127-38829

0.0 KM · EL Toro Resources LLC · Section with this well →

Escondido810-125
Olmos1,679-994
San Miguel2,427-1,742
Austin Chalk3,775-3,090
Eagle Ford—
Pearsall—
Georgetown—
Glen Rose—

9 TOPS · FIRST 8

CR42-127-38338

0.8 KM · CML Exploration, LLC · Section with this well →

Escondido830-147
Olmos1,699-1,016
San Miguel3,529-2,846
Austin Chalk3,878-3,195
Eagle Ford4,823-4,140
Buda5,246-4,563
Georgetown—
Edwards—

10 TOPS · FIRST 8

Comanche42-127-38487

0.8 KM · EL Toro Resources LLC · Section with this well →

Olmos1,748-1,042
San Miguel2,449-1,743
Anacacho3,511-2,805
Austin Chalk3,807-3,101
Eagle Ford—
Edwards—
Escondido—
Georgetown—

10 TOPS · FIRST 8

Comanche42-127-38579

0.8 KM · EL Toro Resources LLC · Section with this well →

Escondido7007
Olmos1,644-937
San Miguel2,416-1,709
Austin Chalk3,756-3,049
Pearsall—
Eagle Ford—
Edwards—
Georgetown—

9 TOPS · FIRST 8

Comanche42-127-38578

0.8 KM · EL Toro Resources LLC · Section with this well →

Escondido7007
Olmos1,759-1,052
San Miguel2,412-1,705
Austin Chalk3,736-3,029
Edwards—
Glen Rose—
Georgetown—
Eagle Ford—

9 TOPS · FIRST 8

CR42-127-38331

1.9 KM · CML Exploration, LLC · Section with this well →

Escondido791-111
Olmos1,698-1,018
Austin Chalk3,836-3,156
Eagle Ford4,766-4,086
Buda5,188-4,508
Georgetown—
San Miguel—
Pearsall—

10 TOPS · FIRST 8

Comanche42-127-38933

1.9 KM · EL Toro Resources LLC · Section with this well →

Escondido720-6
Olmos1,709-995
San Miguel2,574-1,860
Austin Chalk3,686-2,972
Georgetown—
Glen Rose—
Edwards—
Pearsall—

9 TOPS · FIRST 8

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