FIELDS · TEXAS · FIELD 14611520
Cage Ranch (7400)
Field · District 04 · Brooks County
Cage Ranch (7400) is an RRC field with 3 leases on file reported by 13 operators, in Brooks County.
No volume has been reported since July 2026.
Safari Production Company, Inc. holds the most, 2 leases and 226 barrels of oil lifetime.
Lifetime, the field has reported 226 barrels of oil and 180,189 mcf of gas, across 1 oil and 2 gas leases.
- 3
- leases on file · 1 oil, 2 gas
- 0
- leases reporting volume
- 13
- operators, all time
- 0
- active wellbores of 5 · 0 operators today
- 0
- bbl oil, 12 months through Apr 2026
- 0
- Mcf gas, same 12 months
- 226
- bbl oil, lifetime · 180,189 Mcf gas
Every well completed in it, searchable →
Reported production by month
Last 12 months 0 · prior 12 0
Cage Ranch (7400): Oil by month.
Operators
BY LIFETIME OIL ON THEIR LEASES · TOP 2
| Operator | Leases | Oil, bbl | Gas, Mcf | Last reported |
|---|---|---|---|---|
| Safari Production Company, Inc. | 2 | 226 | 24 | Jul 2026 |
| Texron Operating, LLC | 1 | 0 | 180K | Jul 2026 |
Counties
- Brooks County → 3 leases
Latest completions
BY COMPLETION DATE
| Well | Operator | County | Completed | Top perf, ft | Oil, 12 mo | Gas, 12 mo |
|---|---|---|---|---|---|---|
| Cage Ranch 656 #1 | Safari Production Company Inc. | Brooks | Oct 2, 2015 | — | 0 | 0 |
| Cage Ranch 725 #1 | Texron Operating LLC | Brooks | Sep 22, 1999 | — | 0 | 0 |
| Cage Ranch -a- #5 | Texas Fuel Company | Brooks | Mar 10, 1989 | — | 0 | 0 |
| Cage Estate -D- #1 C | Texas Fuel Company | Brooks | Jan 10, 1969 | — | 0 | 0 |
About this data
Field 14611520 from RRC PDQ lease reports: lifetime totals and lease and operator counts from the field summary; the monthly series summed from every lease report naming the field, cut at the statewide reported-through month, Apr 2026. Counties from the wells completed on each lease. Completions are the wellbores the RRC schedule ties to the field. Nothing is estimated.
Developers: this page as JSON is GET /v1/data/fields/tx/14611520, documented in the API reference.