LEASES · O-13-30263 · OIL · DISTRICT 09
Jan Lee
No volume since Mar 2015Dry Creek Operating, LLC · Cooke County · Newark, East (Barnett Shale) field
Jan Lee is an RRC oil lease (O-13-30263) in Cooke County operated by Dry Creek Operating, LLC, with one well completed on it.
It has reported 6.22K barrels of oil and 55.6K mcf of gas since January 2004, last reporting volume in March 2015 (statewide data runs through April 2026).
No volume was reported in the last 12 months; the last was in March 2015.
6 operators have filed production on it, most recently Dry Creek Operating, LLC since August 2022.
- 6.22K
- bbl oil, all reported
- 55.6K
- mcf gas incl. casinghead
- 0
- bbl oil, last 12 reported
- —
- vs the 12 before
- 1
- wells completed on it
- 809
- peak month, bbl (Feb 2004)
PDQ LEASE REPORTS · FIRST JAN 2004 · LAST VOLUME MAR 2015 · 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 0
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.
- Merritt Operating, Inc.Jan 2004 → Jun 2010 · 78 mo
- Smith Pipe of AbileneJul 2010 → Sep 2010 · 3 mo
- Rife Energy Operating, Inc.Oct 2010 → Jan 2017 · 76 mo
- Precision Oil Operating, LLCFeb 2017 → Mar 2019 · 26 mo
- Azteca Petroleum, LLCApr 2019 → Jul 2022 · 40 mo
- Dry Creek Operating, LLCAug 2022 → Jul 2026 · 48 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-13-30263, documented in the API reference.