LEASES · O-14-7883 · OIL · DISTRICT 10

Cooper 435

No volume since Apr 2020

Highmark Energy Operating, LLC · Lipscomb County · Lipscomb (Cleveland) field

Cooper 435 is an RRC oil lease (O-14-7883) in Lipscomb County operated by Highmark Energy Operating, LLC, with 4 wells completed on it.

It has reported 196K barrels of oil and 2.15M mcf of gas since July 2008, last reporting volume in April 2020 (statewide data runs through April 2026).

No volume was reported in the last 12 months; the last was in April 2020.

2 operators have filed production on it, most recently Highmark Energy Operating, LLC since February 2022.

196K
bbl oil, all reported
2.15M
mcf gas incl. casinghead
0
bbl oil, last 12 reported
—
vs the 12 before
4
wells completed on it
7.58K
peak month, bbl (Jan 2009)

PDQ LEASE REPORTS · FIRST JUL 2008 · LAST VOLUME APR 2020 · 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

05001K1.5K2014201520162017201820192020202120222023

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

05K10K15K2014201520162017201820192020202120222023

Who reported it

Each run of months one operator filed the production report, oldest first.

  1. EOG Resources, Inc.Jul 2008 → Jan 2022 · 163 mo
  2. Highmark Energy Operating, LLCFeb 2022 → Jul 2023 · 18 mo

Wells on the lease

FROM COMPLETION REPORTS · PRODUCTION ABOVE IS THEIR TOTAL

4

wells completed on the lease

Plugged
4

Newest permits

All 4 wells, searchable →

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-7883, documented in the API reference.