WELL · 42-077-35232 · DISTRICT 9

Leda Roe #2

Y

Clay County · KRS (Marble Falls) field · Producing  · Vertical

Leda Roe #2 (API 42-077-35232) is a well in Clay County operated by Rife Energy Operating Inc., completed August 24, 2015 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued June 8, 2015, permitted to 6,500 ft.

Completion filings report 10 formation tops, including Cisco, Gunsight, Weir, Canyon.

Its lease has reported 6.55K barrels of oil and 67.7K mcf of gas since August 2015, last reporting in July 2026.

Operator of record

Rife Energy Operating Inc.

Fort Worth, TX · P-5 Y, filed May 4, 2026 · 127 permits on file · (817) 991-4498

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleRife Energy Operating Inc.
Production reportsRife Energy Operating, Inc.through Apr 2026
Latest permitRife Energy Operating, Inc.Jun 8, 2015
6,500
total depth, ft
2
permits on file
Jun 8, 2015
last permit issued
Aug 24, 2015
completed
6.55K
cumulative oil, bbl
67.7K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2015 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 24, 2015
Shut in
—
Plugged
—

Operator's P-5 on the schedule: 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.

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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Leda Roe O-13-33462KRS (Marble Falls)Rife Energy Operating, Inc.16.55K67.7KAug 2015 – Jul 2026

Gas, mcf lease total

Last 12 months 3,585 · prior 12 4,605(-22%)

05001K202420252026

Oil, barrels lease total

Last 12 months 458 · prior 12 571(-20%)

050100150202420252026

Chain of custody

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

  1. 1Rife Energy Operating, Inc.Aug 2015 → Apr 2026
  2. 2Azteca Petroleum, LLCFeb 2022 → Mar 2022

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
807174-98DrillRife Energy Operating, Inc.Feb 18, 2016Jun 8, 2015Jun 30, 20156,500
807174-99DrillRife Energy Operating, Inc.Jun 3, 2015Jun 8, 2015Jun 30, 20156,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-33462————

Formation tops

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

FormationMD ftSubsea
CiscoCISCO SERIES550493
GunsightGUNSIGHT SAND870173
Weir2,540-1,497
Canyon2,700-1,657
Granite Wash——
Mobley Sand——
Overcharged Disposal Zone - 4 MI——
StrawnSTRAWN SAND——
Thomas Sand——
Undetermined - Gas Producing Zon——

Perforations

Perforated and open-hole intervals.

FromToType
5,8005,810Perforated
5,8125,832Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62535412.25215 S
5.56,3747.875275 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
00Apr 5, 2016Feb 22, 2016Yes

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