LEASES · O-3-24246 · OIL · DISTRICT 03
Pipkin
No volume since Jan 2003Zone Ridge Operating, LLC · Jefferson County · Jabo (L. Hackberry 8570) field
Pipkin is an RRC oil lease (O-3-24246) in Jefferson County operated by Zone Ridge Operating, LLC, with one well completed on it.
It has reported 18.9K barrels of oil and 20.4K mcf of gas since December 2001, last reporting volume in January 2003 (statewide data runs through April 2026).
No volume was reported in the last 12 months; the last was in January 2003.
6 operators have filed production on it, most recently Zone Ridge Operating, LLC since January 2026.
- 18.9K
- bbl oil, all reported
- 20.4K
- mcf gas incl. casinghead
- 0
- bbl oil, last 12 reported
- —
- vs the 12 before
- 1
- wells completed on it
- 2.16K
- peak month, bbl (Jan 2002)
PDQ LEASE REPORTS · FIRST DEC 2001 · LAST VOLUME JAN 2003 · 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.
- Eex E&P Company, L.P.Dec 2001 → Jul 2003 · 20 mo
- Newfield Exploration CompanyAug 2003 → Feb 2004 · 7 mo
- Magnum Producing, LPMar 2004 → Jun 2025 · 256 mo
- Mag Exploration LLCJul 2025 → Jul 2025 · 1 mo
- Hicks Exploration, LLCAug 2025 → Dec 2025 · 5 mo
- Zone Ridge Operating, LLCJan 2026 → Jul 2026 · 7 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-3-24246, documented in the API reference.