LEASES · O-14-7492 · OIL · DISTRICT 10
Coble 64
No volume since May 2024Palo Duro Resources LLC · Hutchinson County · Shire (Simpson) field
Coble 64 is an RRC oil lease (O-14-7492) in Hutchinson County operated by Palo Duro Resources LLC, with one well completed on it.
It has reported 73.3K barrels of oil and 20.3K mcf of gas since January 2004, last reporting volume in May 2024 (statewide data runs through April 2026).
No volume was reported in the last 12 months; the last was in May 2024.
6 operators have filed production on it, most recently Palo Duro Resources LLC since June 2020.
- 73.3K
- bbl oil, all reported
- 20.3K
- mcf gas incl. casinghead
- 0
- bbl oil, last 12 reported
- —
- vs the 12 before
- 1
- wells completed on it
- 2.75K
- peak month, bbl (Mar 2005)
PDQ LEASE REPORTS · FIRST JAN 2004 · LAST VOLUME MAY 2024 · STATEWIDE DATA THROUGH APR 2026
Oil by month
Barrels reported on Form PR for the whole lease. The latest months are revised upward as late reports arrive.
Last 12 months 0 · prior 12 12(-100%)
Gas by month
Gas-well gas plus casinghead gas, mcf. On an oil lease all gas is reported as casinghead. The latest months are revised upward as late reports arrive.
Last 12 months 0 · prior 12 0
Who reported it
Each run of months one operator filed the production report, oldest first.
- Burnett Oil Co., Inc.Jan 2004 → Jun 2005 · 18 mo
- Latigo Petroleum Texas, LPJul 2005 → Feb 2009 · 44 mo
- Latigo Petroleum, Inc.Mar 2009 → Apr 2011 · 26 mo
- Hadaway Consult and Engineer,llcMay 2011 → Oct 2012 · 18 mo
- Tom Coble Oil & Gas LPNov 2012 → May 2020 · 91 mo
- Palo Duro Resources LLCJun 2020 → Jul 2026 · 74 mo
Wells on the lease
FROM COMPLETION REPORTS · PRODUCTION ABOVE IS THEIR TOTAL
About this data
Monthly oil, gas, and casinghead from the RRC PDQ production dump, which lags the reporting month by two to three months; figures shown through Apr 2026. Wells from completion reports; operator runs from who filed each month's report.
Developers: this page as JSON is GET /v1/data/leases/tx/o-14-7492, documented in the API reference.