LEASES · O-10-45241 · OIL · DISTRICT 08
C.G. Ludeman 'B'
COG Operating LLC · Loving County · Phantom (Wolfcamp) field
C.G. Ludeman 'B' is an RRC oil lease (O-10-45241) in Loving County operated by Cog Operating LLC, with one well completed on it.
It has reported 3.86K barrels of oil and 22 mcf of gas since March 2013, last reporting volume in March 2013 (statewide data runs through April 2026).
No volume was reported in the 12 months through April 2026; the last was in March 2013.
4 operators have filed production on it, most recently Cog Operating LLC since August 2018.
- 3.86K
- bbl oil, all reported
- 22
- mcf gas incl. casinghead
- 0
- bbl oil, 12 months through Apr 2026
- —
- vs the 12 before
- 1
- wells completed on it
- 3.86K
- peak month, bbl (Mar 2013)
PDQ LEASE REPORTS · FIRST MAR 2013 · LAST VOLUME MAR 2013 · 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.
12 months through Apr 2026 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.
12 months through Apr 2026 0 · prior 12 0
Who reported it
Each run of months one operator filed the production report, oldest first.
- Endeavor Energy Resources L.P.Mar 2013 → Aug 2015 · 30 mo
- EOG Resources, Inc.Sep 2015 → Feb 2017 · 18 mo
- RSP Permian, LLCMar 2017 → Jul 2018 · 17 mo
- COG Operating LLCAug 2018 → Sep 2021 · 38 mo
Wells on the lease
FROM COMPLETION REPORTS · PRODUCTION ABOVE IS THEIR TOTAL
1
wells completed on the lease
- Not on Schedule
- 1
Operates them now
Newest permits
- 30130278 #1HAug 31, 2012
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-10-45241, documented in the API reference.