LEASES · O-10-47262 · OIL · DISTRICT 08

Lea, P.J. et AL

No volume since Jan 2016

Stronghold Energy II Oper, LLC · Crane County · Lea, South (Wolfcamp) field

Lea, P.J. ET AL is an RRC oil lease (O-10-47262) in Crane County operated by Stronghold Energy II Oper, LLC, with 2 wells completed on it.

It has reported 215 barrels of oil and 21 mcf of gas since September 2015, last reporting volume in January 2016 (statewide data runs through April 2026).

No volume was reported in the last 12 months; the last was in January 2016.

2 operators have filed production on it, most recently Stronghold Energy II Oper, LLC since January 2019.

215
bbl oil, all reported
21
mcf gas incl. casinghead
0
bbl oil, last 12 reported
—
vs the 12 before
2
wells completed on it
107
peak month, bbl (Sep 2015)

PDQ LEASE REPORTS · FIRST SEP 2015 · LAST VOLUME JAN 2016 · 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

050100150201620172018201920202021

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

051015201620172018201920202021

Who reported it

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

  1. Devon Energy Production Co, L.P.Sep 2015 → Dec 2018 · 40 mo
  2. Stronghold Energy II Oper, LLCJan 2019 → Nov 2021 · 35 mo

Wells on the lease

FROM COMPLETION REPORTS · PRODUCTION ABOVE IS THEIR TOTAL

2

wells completed on the lease

Not on Schedule
1
Plugged
1

Newest permits

All 2 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-10-47262, documented in the API reference.