LEASES · G-13-57066 · GAS · DISTRICT 09
Fouts-Beavers Unit
No volume since Mar 2018Eagleridge Operating, LLC · Boonsville (Bend Congl., Gas) field
Fouts-Beavers Unit is an RRC gas lease (G-13-57066) in the Boonsville (Bend Congl., Gas) field operated by Eagleridge Operating, LLC, with one well completed on it.
It has reported 114K mcf of gas since January 1993, last reporting volume in March 2018 (statewide data runs through April 2026).
No volume was reported in the last 12 months; the last was in March 2018.
7 operators have filed production on it, most recently Eagleridge Operating, LLC since March 2022.
- 114K
- mcf gas, all reported
- 0
- bbl condensate and oil
- 0
- mcf gas, last 12 reported
- —
- vs the 12 before
- 1
- wells completed on it
- —
- peak month, bbl
PDQ LEASE REPORTS · FIRST JAN 1993 · LAST VOLUME MAR 2018 · 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.
Last 12 months 0 · prior 12 0
Who reported it
Each run of months one operator filed the production report, oldest first.
- Texas Exploration & Prod. Co.Jan 1993 → Dec 1995 · 36 mo
- Brammer Supply, Inc.Jan 1996 → Jul 1997 · 19 mo
- Ryder Scott Oil CompanyAug 1997 → Dec 2005 · 101 mo
- Ryder Scott Management, LLCJan 2006 → Mar 2018 · 147 mo
- 1849 Energy Partners, LLCApr 2018 → Oct 2018 · 7 mo
- 1849 Energy Partners Oprtng, LLCNov 2018 → Feb 2022 · 40 mo
- Eagleridge Operating, LLCMar 2022 → Jul 2026 · 53 mo
Wells on the lease
FROM COMPLETION REPORTS · PRODUCTION ABOVE IS THEIR TOTAL
1
wells completed on the lease
- Temp Abandoned
- 1
Operates them now
Newest permits
- — #1—
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-57066, documented in the API reference.