FIELDS · TEXAS · FIELD 14433630
Cabeza Creek (Wilcox Massive)
Field · District 02 · Goliad County · Wilcox Massive in every state →
Cabeza Creek (Wilcox Massive) is an RRC field with 2 leases on file reported by 5 operators, in Goliad County.
Zone Ridge Operating, LLC holds the most, 1 lease and 9,722 mcf of gas lifetime.
Lifetime, the field has reported 1,097 barrels of oil and 10,872 mcf of gas, across 1 oil and 1 gas leases.
- 2
- leases on file · 1 oil, 1 gas
- 0
- leases reporting volume
- 5
- operators, all time
- 0
- active wellbores of 3 · 0 operators today
- 0
- bbl oil, 12 months through Aug 2026
- 0
- Mcf gas, same 12 months
- 1,097
- bbl oil, lifetime · 10,872 Mcf gas
Every well completed in it, searchable →
Operators
BY LIFETIME OIL ON THEIR LEASES · TOP 2
| Operator | Leases | Oil, bbl | Gas, Mcf | Last reported |
|---|---|---|---|---|
| Zone Ridge Operating, LLC | 1 | 1.05K | 9.72K | Apr 2011 |
| Overly Operating Co. | 1 | 43 | 1.15K | Jun 1994 |
Counties
- Goliad County → 2 leases
Latest completions
BY COMPLETION DATE
| Well | Operator | County | Completed | Top perf, ft | Oil, 12 mo | Gas, 12 mo |
|---|---|---|---|---|---|---|
| Reed D. M. #1 | Zone Ridge Operating LLC | Goliad | Nov 1, 2005 | — | — | — |
| Pettus Unit #52 | Nog Production & Operating LLC | Goliad | Jan 19, 1991 | — | — | — |
| Lude W.C. #1D | Overly Operating Co. | Goliad | Jul 15, 1977 | — | — | — |
About this data
Field 14433630 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, Aug 2026. Oil includes condensate from gas leases and gas includes casinghead gas from oil leases, as the RRC totals them. Counties from the wells completed on each lease. Completions are the wellbores the RRC schedule ties to the field. The formation, Wilcox Massive, is read from the field's name. Nothing is estimated.
Developers: this page as JSON is GET /v1/data/fields/tx/14433630, documented in the API reference.