LEASES · G-13-254159 · GAS · DISTRICT 09

Bransom

No volume since Oct 2024

Eagleridge Operating, LLC · Johnson County · Newark, East (Barnett Shale) field

Bransom is an RRC gas lease (G-13-254159) in Johnson County operated by Eagleridge Operating, LLC, with one well completed on it.

It has reported 1.22M mcf of gas since November 2009, last reporting volume in October 2024 (statewide data runs through April 2026).

No volume was reported in the 12 months through April 2026; the last was in October 2024.

5 operators have filed production on it, most recently Eagleridge Operating, LLC since July 2017.

1.22M
mcf gas, all reported
0
bbl oil, all reported
0
mcf gas, 12 months through Apr 2026
—
vs the 12 before
1
wells completed on it
—
peak month, bbl

PDQ LEASE REPORTS · FIRST NOV 2009 · LAST VOLUME OCT 2024 · STATEWIDE DATA THROUGH APR 2026

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

02K4K6K2017201820192020202120222023202420252026

Who reported it

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

  1. Williams Prod. Gulf Coast, L.P.Sep 2009 → Jan 2012 · 29 mo
  2. WPX Energy Gulf Coast, LPFeb 2012 → May 2012 · 4 mo
  3. Premier Natural Resources Ii,llcJun 2012 → Feb 2015 · 33 mo
  4. Trinity River Energy Oper, LLCMar 2015 → Jun 2017 · 28 mo
  5. Eagleridge Operating, LLCJul 2017 → Jul 2026 · 109 mo

Wells on the lease

FROM COMPLETION REPORTS · PRODUCTION ABOVE IS THEIR TOTAL

1

wells completed on the lease

Producing
1

Operates them now

Newest permits

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/g-13-254159, documented in the API reference.