WELL · 42-127-38971 · DISTRICT 1

Yett Ranch #8872H

Y

Dimmit County · Briscoe Ranch (Eagleford) field · Producing  · Horizontal

Yett Ranch #8872H (API 42-127-38971) is a horizontal well in Dimmit County operated by El Toro Resources LLC, completed November 19, 2024 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued October 4, 2024, permitted to 5,800 ft.

Completion filings report 9 formation tops, including Escondido, Olmos, San Miguel, Austin Chalk.

Its lease has reported 58.5K barrels of oil and 97.8K mcf of gas since November 2024, last reporting in July 2026. The lease carries 2 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 LLCOct 4, 2024
5,800
total depth, ft
1
permits on file
Oct 4, 2024
last permit issued
Nov 19, 2024
completed
58.5K
cumulative oil, bbl
97.8K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Nov 2024 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Nov 19, 2024
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

28.478370, -100.008156

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Yett Ranch O-1-21630Briscoe Ranch (Eagleford)EL Toro Resources LLC258.5K97.8KNov 2024 – Jul 2026

Oil, barrels lease total

Last 12 months 15,526 · prior 12 42,977(-64%)

010K20K30K202420252026

Gas, mcf lease total

Last 12 months 64,610 · prior 12 33,148(+95%)

05K10K15K202420252026

Chain of custody

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

  1. 1EL Toro Resources LLCDec 2024 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
902967-99DrillEL Toro Resources LLCSep 27, 2024Oct 4, 2024Oct 7, 20245,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-21630————

Formation tops

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

FormationMD ftSubsea
EscondidoESCONDIDO - DISPOSAL1,326-574
OlmosOLMOS - DISPOSAL2,481-1,729
San MiguelSAN MIGUEL - H2S3,162-2,410
Austin ChalkAUSTIN CHALK - H2S4,520-3,768
Eagle FordEAGLE FORD - H2S5,442-4,690
EdwardsEDWARDS - H2S——
GeorgetownGEORGETOWN - H2S——
Glen RoseGLEN ROSE - DISPOSAL——
Pearsall——

Perforations

Perforated and open-hole intervals.

FromToType
6,12411,084Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,00212.25315 S
5.511,1078.751,987 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
00Mar 17, 2025Feb 26, 2025Yes

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 →

Yett Ranch42-127-38970

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

Escondido1,331-579
Olmos2,489-1,737
San Miguel3,168-2,416
Austin Chalk4,534-3,782
Eagle Ford—
Pearsall—
Glen Rose—
Georgetown—

9 TOPS · FIRST 8

Yett Ranch42-127-38972

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

Escondido1,322-570
Olmos2,480-1,728
San Miguel3,243-2,491
Austin Chalk4,528-3,776
Eagle Ford5,453-4,701
Glen Rose—
Edwards—
Pearsall—

9 TOPS · FIRST 8

Latham-McKnight42-127-37034

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

Escondido1,540-770
Olmos2,115-1,345
San Miguel3,040-2,270
Austin Chalk4,330-3,560
Eagle Ford5,379-4,609
Pearsall—
Glen Rose—
Georgetown—

9 TOPS · FIRST 8

Briscoe-McKnight42-127-38477

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

Escondido1,504-738
Olmos2,487-1,721
San Miguel3,445-2,679
Austin Chalk4,765-3,999
Pearsall—
Edwards—
Georgetown—
Glen Rose—

9 TOPS · FIRST 8

Briscoe-McKnight42-127-38415

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

Escondido1,000-231
Olmos2,600-1,831
San Miguel3,300-2,531
Anacacho4,541-3,772
Austin Chalk4,748-3,979
Glen Rose—
Georgetown—
Edwards—

10 TOPS · FIRST 8

Briscoe-McKnight42-127-38369

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

Escondido1,395-667
Olmos2,344-1,616
San Miguel3,200-2,472
Austin Chalk4,529-3,801

Latham McKnight42-127-37854

5.0 KM · Endeavor Natural Gas, LP · Section with this well →

Olmos1,900-1,092
San Miguel2,300-1,492
Pearsall—
Escondido—
Austin Chalk—
Eagle Ford—
Edwards—
Glen Rose—

9 TOPS · FIRST 8

Hamilton Ranch42-127-38861

5.2 KM · Grit Oil & Gas Management, LLC · Section with this well →

Olmos2,088-1,282
San Miguel2,916-2,110
Glen Rose—
Pearsall—
Georgetown—
Escondido—
Edwards—
Eagle Ford—

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