FIELDS · TEXAS · FIELD 32047666

Fort Griffin, E. (Miss)

Field · District 7B · Shackelford County · Miss in every state →

Fort Griffin, E. (Miss) is an RRC field with 3 leases on file reported by 8 operators, in Shackelford County.

Beehive Operating, LLC holds the most, 2 leases and 1,518 barrels of oil lifetime.

Lifetime, the field has reported 1,518 barrels of oil and 1,889 mcf of gas.

3
leases on file
0
leases reporting volume
8
operators, all time
0
active wellbores of 7 · 0 operators today
0
bbl oil, 12 months through Apr 2026
0
Mcf gas, same 12 months
1,518
bbl oil, lifetime · 1,889 Mcf gas

Every well completed in it, searchable →

Operators

BY LIFETIME OIL ON THEIR LEASES · TOP 2

OperatorLeasesOil, bblGas, McfLast reported
Beehive Operating, LLC21.52K1.89KJan 2012
L.C.S. Production Company100—

All 3 leases in Fort Griffin, E. (Miss), searchable →

Counties

Latest completions

BY COMPLETION DATE

WellOperatorCountyCompletedTop perf, ftOil, 12 moGas, 12 mo
Hilltex River Ranch 5 #1Beehive Operating LLCShackelfordSep 29, 2006———
Walker-Buckler Trust/TR 40A/Roco #2Beehive Operating LLCShackelfordSep 27, 1991———
Walker-Buckler B.s.&f. a #1Jones Co.ShackelfordJan 13, 1986———
Walker-Buckler Trust/TR 40A/SWD #1DBeehive Operating LLCShackelfordAug 31, 1967———
Ledbetter #1L.C.S. Production CompanyShackelfordSep 8, 1964———
Ledbetter #1DL.C.S. Production CompanyShackelfordSep 8, 1964———

About this data

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

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