TEXAS · WELLS · LOVING COUNTY · RUDD DRAW 29-3 LEASE · API 42-301-32327 · DISTRICT 7B

Rudd Draw 29-3 #3H

Y

Loving County · Phantom (Wolfcamp) field · Producing  · Horizontal

Fields on the latest permit · any of 2
Phantom (Wolfcamp) · Two Georges (Bone Spring)
Not one formation; the well must be completed in one of them, and no target formation is stated.

Rudd Draw 29-3 #3H (API 42-301-32327) is a horizontal well in Loving County operated by Cog Operating LLC, completed July 26, 2017 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued September 16, 2014, permitted to 11,833 ft.

It was permitted by Silver Hill Energy Partners, LLC and has since transferred to Cog Operating LLC on the wellbore schedule.

Completion filings report 10 formation tops, including Red Bluff, Bell Canyon, Delaware, Cherry Canyon.

Its lease has reported 4.11M barrels of oil and 7.73M mcf of gas since September 2015, last reporting volume in April 2026. The lease carries 12 wells, so these are lease totals, not this well alone.

Operator of record

COG Operating LLC

Permitted by Silver Hill Energy Partners, LLC; the EWA schedule now lists a different operator.

Based in
Midland, TX
P-5 status
Active – Extension (X)
P-5 last filed
Jun 2, 2026
Permits on file
4,568
Phone
(432) 683-7443

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCOG Operating LLC
Production reportsCOG Operating LLCthrough Apr 2026
Latest permitSilver Hill Energy Partners, LLCSep 16, 2014

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

11,833
total depth, ft
1
permits on file
Sep 16, 2014
last permit issued
Jul 26, 2017
completed
4.11M
cumulative oil, bbl
7.73M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2015 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 26, 2017
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

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; they carry 12 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Rudd Draw 29-3 O-10-46941Phantom (Wolfcamp)COG Operating LLC124.11M7.73MSep 2015 – Apr 2026

Oil, barrels lease total

Last 12 months 90,181 · prior 12 143,083(-37%)

010K20K202420252026

Gas, mcf lease total

Last 12 months 150,951 · prior 12 390,661(-61%)

020K40K60K202420252026

Chain of custody

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

  1. 1Silver Hill Energy Partners, LLCSep 2015 → Feb 2017
  2. 2RSP Permian, LLCMar 2017 → Jul 2018
  3. 3COG Operating LLCAug 2018 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
794969-99DrillSilver Hill Energy Partners, LLCAug 26, 2014Sep 16, 2014Jun 27, 201513,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Jul 26, 2017Rudd Draw 29-3 O-10-46941Phantom (Wolfcamp)COG Operating LLCProducing11,833

Formation tops

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

FormationMD ftSubsea
Red Bluff3,900-810
Bell Canyon5,113-2,023
Delaware5,113-2,023
Cherry Canyon6,284-3,194
Brushy Canyon7,363-4,273
Bone SpringBONE SPRINGS8,885-5,795
Wolfcamp11,756-8,666
AtokaATOKA - HIGH PRESSURE——
Pennsylvanian——
Red Bluff——
Strawn——

Perforations

Perforated and open-hole intervals.

FromToType
12,24216,486Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3751,21317.5805 S
9.6255,05512.251,090 S
712,0408.751,400 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00May 1, 2018Apr 18, 2018Yes
00Oct 29, 2015Oct 8, 2015—
00Oct 27, 2015Sep 28, 2015Yes

Well logs

1 log loaded from the RRC's log index, the latest received Sep 5, 2018. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
OtherSpans Red Bluff, Bell Canyon, Delaware, Cherry Canyon, Brushy Canyon, Bone SpringTIFF5,010 to 11,744Sep 5, 201810.5

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it. The University Lands library has no per-well link: then paste it into its 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/30132327, documented in the API reference.