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

Riley

No volume since Dec 2024

Mag Exploration LLC · Lipscomb, S.E. (Cleveland) field

Riley is an RRC oil lease (O-14-8715) in the Lipscomb, S.E. (Cleveland) field operated by Mag Exploration LLC, with one well completed on it.

It has reported 4.1K barrels of oil and 22.1K mcf of gas since December 2011, last reporting volume in December 2024 (statewide data runs through April 2026).

No volume was reported in the last 12 months; the last was in December 2024.

2 operators have filed production on it, most recently Mag Exploration LLC since December 2025.

4.1K
bbl oil, all reported
22.1K
mcf gas incl. casinghead
0
bbl oil, last 12 reported
—
vs the 12 before
1
wells completed on it
217
peak month, bbl (Dec 2015)

PDQ LEASE REPORTS · FIRST DEC 2011 · LAST VOLUME DEC 2024 · 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

0501001502017201820192020202120222023202420252026

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 130(-100%)

05001K2017201820192020202120222023202420252026

Who reported it

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

  1. Zephyr Lone Star Oper Co.,l.l.c.Dec 2011 → Nov 2025 · 168 mo
  2. Mag Exploration LLCDec 2025 → Jul 2026 · 8 mo

Wells on the lease

FROM COMPLETION REPORTS · PRODUCTION ABOVE IS THEIR TOTAL

1

wells completed on the lease

NO Type on File
1

Newest permits

  • — #1—

All 1 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-8715, documented in the API reference.