FIELDS · TEXAS · FIELD 72585503

Post Oak (Ellenburger B)

Field · District 09 · Jack County and 1 more · Ellenburger B in every state →

Post Oak (Ellenburger B) is an RRC field with 2 leases on file reported by 11 operators, in Jack County.

No volume has been reported since December 2016.

Legacy Exploration, LLC I holds the most, 1 lease and 35,917 mcf of gas lifetime.

Lifetime, the field has reported 7,915 barrels of oil and 38,568 mcf of gas.

2
leases on file
0
leases reporting volume
11
operators, all time
0
active wellbores of 4 · 0 operators today
0
bbl oil, 12 months through Apr 2026
0
Mcf gas, same 12 months
7,915
bbl oil, lifetime · 38,568 Mcf gas

Every well completed in it, searchable →

Reported production by month

12 months through Apr 2026 0 · prior 12 0

02040602017201820192020202120222023202420252026

Post Oak (Ellenburger B): Oil by month.

Operators

BY LIFETIME OIL ON THEIR LEASES · TOP 2

OperatorLeasesOil, bblGas, McfLast reported
Legacy Exploration, LLC I15.81K35.9KDec 2016
Person Oil Co.12.11K2.65KMay 1994

All 2 leases in Post Oak (Ellenburger B), searchable →

Counties

Latest completions

BY COMPLETION DATE

WellOperatorCountyCompletedTop perf, ftOil, 12 moGas, 12 mo
Matlock #1Henco EnergyClayMar 2, 1985———
Cleveland #d 1Legacy Exploration LLC IJackOct 20, 1984———
Post Oak #2Person Oil Co.JackSep 26, 1984———
Post Oak #1Person Oil Co.JackApr 4, 1984———

About this data

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

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