FIELDS · TEXAS · FIELD 84343080
Smooth Bore (Ellenburger)
Field · District 09 · Jack County · Ellenburger in every state →
Smooth Bore (Ellenburger) is an RRC field with 3 leases on file reported by 2 operators, in Jack County.
No volume has been reported since March 2024.
G & F Oil, Inc. holds the most, 3 leases and 49,259 barrels of oil lifetime.
Lifetime, the field has reported 49,259 barrels of oil and 162,193 mcf of gas.
- 3
- leases on file
- 0
- leases reporting volume
- 2
- operators, all time
- 0
- active wellbores of 3 · 0 operators today
- 0
- bbl oil, 12 months through Apr 2026
- 0
- Mcf gas, same 12 months
- 49,259
- bbl oil, lifetime · 162,193 Mcf gas
Every well completed in it, searchable →
Reported production by month
12 months through Apr 2026 0 · prior 12 0
Smooth Bore (Ellenburger): Oil by month.
Operators
BY LIFETIME OIL ON THEIR LEASES · TOP 1
| Operator | Leases | Oil, bbl | Gas, Mcf | Last reported |
|---|---|---|---|---|
| G & F Oil, Inc. | 3 | 49.3K | 162K | Mar 2024 |
Counties
- Jack County → 3 leases
Latest completions
BY COMPLETION DATE
| Well | Operator | County | Completed | Top perf, ft | Oil, 12 mo | Gas, 12 mo |
|---|---|---|---|---|---|---|
| Henderson Unit #1 | G & F Oil Inc. | Jack | Dec 21, 2005 | — | — | — |
| Perkins Melinda #2 | G & F Oil Inc. | Jack | Oct 27, 2004 | — | — | — |
| Alta Briscoe #1 | G & F Oil Inc. | Jack | Aug 4, 2003 | — | — | — |
About this data
Field 84343080 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. 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, Ellenburger, is read from the field's name. Nothing is estimated.
Developers: this page as JSON is GET /v1/data/fields/tx/84343080, documented in the API reference.