LEASES · G-3-200964 · GAS · DISTRICT 03

Big Creek Park

No volume since Feb 2019

Iron Ridge Operating, LLC · Burleson County · Giddings (Austin Chalk, Gas) field

Big Creek Park is an RRC gas lease (G-3-200964) in Burleson County operated by Iron Ridge Operating, LLC, with one well completed on it.

It has reported 639K mcf of gas since February 2004, last reporting volume in February 2019 (statewide data runs through April 2026).

No volume was reported in the last 12 months; the last was in February 2019.

6 operators have filed production on it, most recently Iron Ridge Operating, LLC since October 2025.

639K
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 FEB 2004 · LAST VOLUME FEB 2019 · 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

0242017201820192020202120222023202420252026

Who reported it

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

  1. Trek Resources, Inc.Feb 2004 → May 2014 · 124 mo
  2. BBX Operating, L.L.C.Jun 2014 → Dec 2016 · 31 mo
  3. Brazos Valley Operating, LLCJan 2017 → Feb 2019 · 26 mo
  4. Eagle Valley Development LLCMar 2019 → Apr 2023 · 50 mo
  5. BBX Operating, L.L.C.May 2023 → Sep 2025 · 29 mo
  6. Iron Ridge Operating, LLCOct 2025 → Jul 2026 · 10 mo

Wells on the lease

FROM COMPLETION REPORTS · PRODUCTION ABOVE IS THEIR TOTAL

1

wells completed on the lease

Plugged
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-3-200964, documented in the API reference.