FIELDS · TEXAS · FIELD 802500

After Five (Tannehill)

Field · District 8A · Dickens County · Tannehill in every state →

After Five (Tannehill) is an RRC field with 3 leases on file reported by 2 operators, in Dickens County.

In the 12 months reported through April 2026 it produced 8,903 barrels of oil, down 11% on the year before, from 2 leases reporting volume.

Halliburton Operating Company holds the most, 2 leases and 237,165 barrels lifetime.

Lifetime, the field has reported 237,165 barrels of oil and 0 mcf of gas.

3
leases on file
2
leases reporting volume
2
operators, all time
4
active wellbores of 4 · 2 operators today
8,903
bbl oil, 12 months through Apr 2026 · −11%
0
Mcf gas, same 12 months
237,165
bbl oil, lifetime · 0 Mcf gas

Every well completed in it, searchable →

Reported production by month

Last 12 months 8,903 · prior 12 9,980(-11%)

01K2K2017201820192020202120222023202420252026

After Five (Tannehill): Oil by month.

Operators

BY LIFETIME OIL ON THEIR LEASES · TOP 2

OperatorLeasesOil, bblGas, McfLast reported
Halliburton Operating Company2237K0Jul 2026
HGN Operating I, LLC100Jul 2026

All 3 leases in After Five (Tannehill), searchable →

Counties

Latest completions

BY COMPLETION DATE

WellOperatorCountyCompletedTop perf, ftOil, 12 moGas, 12 mo
Mabel #1HGN Operating I LLCDickensApr 10, 2014—00
Elwanda #4Halliburton Operating CompanyDickensFeb 15, 2013—00
Kathi #1Halliburton Operating CompanyDickensJul 8, 2012—00
Elwanda #2Halliburton Operating CompanyDickensJan 19, 2012—00

About this data

Field 802500 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, Tannehill, is read from the field's name. Nothing is estimated.

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