TEXAS · WELLS · YOAKUM COUNTY · WILDER "C" LEASE · API 42-501-35640 · DISTRICT 7B

Wilder C #15

Y

Yoakum County · Wasson 72 field · Producing  · Vertical

Wilder C #15 (API 42-501-35640) is a well in Yoakum County operated by Occidental Permian Ltd., completed April 13, 2010 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued February 3, 2010, permitted to 8,588 ft.

Completion filings report 6 formation tops, including Yates, Grayburg, Glorieta, Clear Fork.

Its lease has reported 2.04M barrels of oil and 481K mcf of gas since May 2005, last reporting in July 2026. The lease carries 14 wells, so these are lease totals, not this well alone.

Operator of record

Occidental Permian Ltd.

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Feb 2, 2026
Permits on file
6,251
Phone
(713) 215-7000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOccidental Permian Ltd.
Production reportsOccidental Permian Ltd.through Apr 2026
Latest permitOccidental Permian Ltd.Feb 3, 2010
8,588
total depth, ft
1
permits on file
Feb 3, 2010
last permit issued
Apr 13, 2010
completed
2.04M
cumulative oil, bbl
481K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2005 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 13, 2010
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 14 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Wilder "C" O-11-68771Wasson 72Occidental Permian Ltd.142.04M481KMay 2005 – Jul 2026

Oil, barrels lease total

Last 12 months 29,287 · prior 12 43,629(-33%)

02K4K6K202420252026

Gas, mcf lease total

Last 12 months 13,587 · prior 12 14,187(-4%)

01K2K202420252026

Chain of custody

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

  1. 1Occidental Permian Ltd.May 2005 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
688501-99DrillOccidental Permian Ltd.Dec 10, 2009Feb 3, 2010Feb 15, 20108,700

Completions

CompletedLeaseFieldOperatorStatusDepth
Apr 13, 2010Wilder C O-11-68771Wasson 72Occidental Permian Ltd.Producing8,588

Formation tops

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

FormationMD ftSubsea
Yates3,157375
Grayburg4,354-822
Glorieta6,090-2,558
Clear ForkCLEARFORK, UPPER6,341-2,809
Tubb7,596-4,064
Cleafork Lower7,694-4,162

Perforations

Perforated and open-hole intervals.

FromToType
7,7318,326Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,43712.251,070 S
5.58,5878.75340 S
5.5—8.751,720 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
00Jul 1, 2010May 18, 2010Yes
00Jun 9, 2010——

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