WELL · 42-487-33152 · DISTRICT 9

Rcmsu #2 #34

N

Wilbarger County  · Vertical

Rcmsu #2 #34 (API 42-487-33152) is a permitted well in Wilbarger County filed by Slant Operating, LLC; no completion report is on file yet.

The RRC has issued 2 drilling permits in 2018, permitted to 2,700 ft.

Completion filings report 12 formation tops, including Coleman Junction, Cisco, Dyson Sand, Gunsight.

Its 2 leases have reported 140K barrels of oil and 21 mcf of gas since January 1993, last reporting in July 2026. The leases carry 41 wells, so these are lease totals, not this well alone.

Operator of record

Slant Operating, LLC

Lafayette, LA · P-5 Y, filed Oct 4, 2025 · 194 permits on file · (337) 534-0135

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsBurk Royalty Co., Ltd.through Apr 2026
Latest permitSlant Operating, LLCSep 14, 2018
2,700
total depth, ft
2
permits on file
Sep 14, 2018
last permit issued
—
completed
140K
cumulative oil, bbl
21
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

Surface location

33.995206, -99.171906

OpenStreetMap → ·  Google Maps →

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

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Rcmsu #2 O-13-12319Wilbarger County RegularBurk Royalty Co., Ltd.3198K21Jan 1993 – Jul 2026
Waggoner DN O-13-32805Wilbarger County (Special)Burk Royalty Co., Ltd.1042.4K0Dec 2013 – Jul 2026

Oil, barrels lease total

Last 12 months 2,215 · prior 12 3,204(-31%)

0200400600202420252026

Chain of custody

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

  1. 1Johnson & Ernst Operating Co.Jan 1993 → Mar 2018
  2. 2Slant Operating, LLCApr 2018 → Apr 2022
  3. 3Burk Royalty Co., Ltd.May 2022 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
844463-99RecompletionSlant Operating, LLCSep 7, 2018Sep 14, 2018—2,564
836765-99DrillJohnson & Ernst Operating Co.Feb 23, 2018Mar 7, 2018Mar 20, 20182,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-12319————
—— O-13-32805————

Formation tops

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

FormationMD ftSubsea
Coleman JunctionCOLEMAN JUNCTION - CORROSIVE ZON932236
Cisco1,262-94
Dyson Sand1,890-722
GunsightGUNSIGHT LIME2,170-1,002
Noble Lime2,280-1,112
Milham Sand2,397-1,229
Caddo——
Canyon——
King——
KMA——
Palo Pinto——
Strawn——

Perforations

Perforated and open-hole intervals.

FromToType
2,3972,406Perforated
2,4742,479Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6256612.2550 S
4.52,5567.875460 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
00Sep 25, 2018Aug 2, 2018—
00Jun 1, 2018May 18, 2018Yes

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 →

Waggoner DN42-487-33135

0.3 KM · Johnson & Ernst Operating Co. · Section with this well →

Coleman Junction955234
Cisco1,290-101
Dyson Sand1,925-736
Milham Sand2,415-1,226
Palo Pinto—
Caddo—
Strawn—
KMA—

10 TOPS · FIRST 8

Waggoner DN42-487-33068

0.4 KM · Johnson & Ernst Operating Co. · Section with this well →

Coleman Junction950222
Cisco1,290-118
Dyson Sand1,900-728
Milham Sand2,410-1,238
Canyon2,628-1,456
Caddo—
Palo Pinto—
Strawn—

10 TOPS · FIRST 8

Waggoner DN42-487-33162

0.5 KM · Slant Operating, LLC · Section with this well →

Coleman Junction885282
Cisco1,337-170
Milham Sand2,315-1,148
Strawn—
KMA—
King—
Caddo—
Canyon—

10 TOPS · FIRST 8

Waggoner DN42-487-33090

0.6 KM · Johnson & Ernst Operating Co. · Section with this well →

Coleman Junction905236
Cisco1,240-99
King1,660-519
Dyson Sand1,860-719
Milham Sand2,330-1,189
Canyon2,590-1,449
Strawn—
Caddo—

10 TOPS · FIRST 8

Waggoner Ranch Batt #442-487-80865

1.3 KM · Slant Operating, LLC · Section with this well →

Coleman Junction150985
Cisco1,290-155
Gunsight2,180-1,045
Dyson Sand—
Strawn—
KMA—
King—
Canyon—

10 TOPS · FIRST 8

Waggoner DN42-487-33184

1.3 KM · Slant Operating, LLC · Section with this well →

Coleman Junction1501,004
Cisco1,304-150
Milham Sand2,302-1,148
Caddo—
Canyon—
Dyson Sand—
King—
KMA—

10 TOPS · FIRST 8

Waggoner Ranch Batt #442-487-33214

1.9 KM · Slant Operating, LLC · Section with this well →

Coleman Junction1501,004
Dyson Lime1,865-711
Gunsight2,190-1,036
Noble2,250-1,096
1ST Milham2,290-1,136
Landreth2,550-1,396
Canyon3,267-2,113
Strawn3,450-2,296

10 TOPS · FIRST 8

Goner, W.42-487-33271

1.9 KM · Burk Royalty Co., Ltd. · Section with this well →

Coleman Junction932224
Dyson Sand1,882-726
Canyon2,365-1,209
Palo Pinto—
Cisco—
King—
Strawn—
Caddo—

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