FIELDS · TEXAS · FIELD 29797190

Executive (Ellenburger)

Field · District 7C · Crockett County · Ellenburger in every state →

Executive (Ellenburger) is an RRC field with 4 leases on file reported by 2 operators, in Crockett County.

In the 12 months reported through April 2026 it produced 10,911 barrels of oil, up 30% on the year before, from 2 leases reporting volume.

Red Stag Operating, LLC holds the most, 3 leases and 391,346 barrels lifetime.

Lifetime, the field has reported 391,346 barrels of oil and 24,356 mcf of gas, across 2 oil and 2 gas leases.

4
leases on file · 2 oil, 2 gas
2
leases reporting volume
2
operators, all time
1
active wellbores of 3 · 1 operators today
10,911
bbl oil, 12 months through Apr 2026 · +30%
0
Mcf gas, same 12 months
391,346
bbl oil, lifetime · 24,356 Mcf gas

Every well completed in it, searchable →

Reported production by month

Last 12 months 10,911 · prior 12 8,396(+30%)

01K2K2017201820192020202120222023202420252026

Executive (Ellenburger): Oil by month.

Operators

BY LIFETIME OIL ON THEIR LEASES · TOP 2

OperatorLeasesOil, bblGas, McfLast reported
Red Stag Operating, LLC3391K0Jul 2026
Thompson, J. Cleo1024.4KJul 2015

All 4 leases in Executive (Ellenburger), searchable →

Counties

Latest completions

BY COMPLETION DATE

WellOperatorCountyCompletedTop perf, ftOil, 12 moGas, 12 mo
Thompson 68 #3Thompson J. CleoCrockettDec 6, 2003—00
Thompson 93 #1Red Stag Operating LLCCrockettOct 5, 2001—00
Thompson 67 #23Red Stag Operating LLCCrockettSep 8, 1999—00

About this data

Field 29797190 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. The formation, Ellenburger, is read from the field's name. Nothing is estimated.

Developers: this page as JSON is GET /v1/data/fields/tx/29797190, documented in the API reference.