OPERATORS · RRC 902630 · P-5 STATUS Y
WDH Oil Properties, Inc
Abilene, TX
Watch this operatorWdh Oil Properties, Inc has filed no drilling permits in the past 12 months; its most recent permit was issued August 5, 1985.
The RRC wellbore file lists 1 well under its operatorship.
46 drilling permits have been issued to this operator number since 1980; its P-5 organization report was last filed October 15, 1985.
- 0
- permits, last 12 months
- —
- vs prior 12 months (0)
- 0
- counties, 12 months
- 0
- producing wells, of 1 of record
- 0
- leases it reports
- —
- horizontal, 12 months
WINDOWS ON THE RRC ISSUE DATE · COMPUTED OCT 29, 2026
From permit to spud
FROM THE DATES ON ITS W-1 PERMITS · ALL TIME
A permit is a plan, not a well. These figures count only permits old enough to have spudded, six months and more, and read the spud, cancel, and expiry dates the RRC records on each one.
- 24%
- spud rate · 11 of 46 mature permits
- 74
- median days permit to spud · middle half 53–98
- 0
- spuds, last 180 days
- 0%
- cancelled · 0 permits
- 35
- expired undrilled
- 9
- permits a year over 5 active years
Where
Counties by permits in the last 12 months, with all-time permits and current wells of record there.
| County | 12 mo | All time | Wells | Last |
|---|---|---|---|---|
| Runnels county → | — | 21 | 0 | May 29, 1985 |
| Eastland county → | — | 16 | 0 | Aug 25, 1983 |
| Taylor county → | — | 4 | 1 | Oct 6, 1982 |
| Coleman county → | — | 3 | 0 | Aug 5, 1985 |
| Jones county → | — | 2 | 0 | Jun 5, 1984 |
All 46 permits, searchable → · Leases it reports → · On the map →
Formations in its completed wells
Tops reported on completion filings for wells it operates. RRC wellbore file. About tops →
| Formation | Wells | Permitted last 3 yrs |
|---|---|---|
| Palo Pinto | 6 | 0 |
| Caddo | 5 | 0 |
| Ellenburger | 4 | 0 |
| Marble Falls | 3 | 0 |
| Strawn | 2 | 0 |
| Coleman Junction | 1 | 0 |
| Cisco | 1 | 0 |
| Canyon | 1 | 0 |
| Duffer | 1 | 0 |
Production by month
PDQ LEASE REPORTS · REPORTED THROUGH APR 2026
Barrels on leases where this operator filed the production report. Lease-level by design; the latest months are revised upward as late reports arrive. How production is reported →
- 0
- bbl oil, last 12 reported months
- —
- vs the 12 months before
- 0
- mcf gas incl. casinghead, last 12
- 0
- bbl oil since reporting began
No lease production reported under this operator number in the last three years.
Beyond the permit record
RRC wellbore file
Wells of record
- 1
- on the schedule
- 0
- producing
- 0
- shut in
- 0
- injection
- 0
- temp. abandoned
- 1
- plugged
How it got them
- 1
- permitted itself
- 0
- acquired from others
- 16
- permitted, now run by others
Acquired means the well's permit names a different operator than the schedule does today. Transfers and operator numbers →
Permit types
Last 12 months against the prior 12, and all time. A type opens the permit history filtered to it. What the types mean →
| Type | 12 mo | Prior 12 | All time |
|---|---|---|---|
| Drill | 0 | 0 | 44 |
| Other | 0 | 0 | 1 |
| Recompletion | 0 | 0 | 1 |
Fields
RRC regulatory fields with the most wells of record under this operator. The field opens its page; the count opens this operator's wells in it.
| Field | Wells | Producing |
|---|---|---|
| Jocelyn-Varn South (Fry Upper)46620500 | 1 | 0 |
P-5 organization report
As registered with the RRC. About the P-5 →
- Registration
- Status code Y
- Last filed Oct 15, 1985
- Address
- P O Box 5174
- Abilene, TX 79608
- Officers and agents
- Haddox, W. Daniel · Chairman/Resident Texas Agent
- Clayton, Patsy JO · Secretary
Latest permits
NEWEST FIRST BY ISSUE DATE · FILED OR ON WELLS IT NOW OPERATES
About this data
Registration from the RRC P-5 organization report, refreshed weekly. Permits from the OGA049M master and daily daf420 files; wells of record from the EWA wellbore schedule; production from PDQ lease reports at the last vintage; disposal from UIC permits and H-10 reports. Summary figures are rebuilt nightly.
Developers: this page as JSON is GET /v1/data/operators/tx/902630, documented in the API reference.