FIELDS · TEXAS · FIELD 89118500

Texas Concho (3500)

Field · District 7C · Concho County

Texas Concho (3500) is an RRC field with 3 leases on file reported by 4 operators, in Concho County.

Runnels S.w.d.,inc. holds the most, 1 lease and 3,875 barrels of oil lifetime.

Lifetime, the field has reported 3,882 barrels of oil and 4,937 mcf of gas, across 2 oil and 1 gas leases.

3
leases on file · 2 oil, 1 gas
0
leases reporting volume
4
operators, all time
0
active wellbores of 9 · 0 operators today
0
bbl oil, 12 months through Apr 2026
0
Mcf gas, same 12 months
3,882
bbl oil, lifetime · 4,937 Mcf gas

Every well completed in it, searchable →

Operators

BY LIFETIME OIL ON THEIR LEASES · TOP 3

OperatorLeasesOil, bblGas, McfLast reported
Runnels S.w.d.,inc.13.88K4.93KApr 2012
MGM Oil & Gas Inc.177Jun 1994
Martin Exploration100—

All 3 leases in Texas Concho (3500), searchable →

Counties

Latest completions

BY COMPLETION DATE

WellOperatorCountyCompletedTop perf, ftOil, 12 moGas, 12 mo
Hartgrove 132-D #1Runnels S.W.D. Inc.ConchoMay 10, 1987———
Dutton Harold #1MGM Oil & Gas Inc.ConchoDec 19, 1986———
Dutton Harold #11MGM Oil & Gas Inc.ConchoNov 27, 1986———
August Pope #4Nitram Oil and Gas Inc.ConchoOct 15, 1986———
Dutton Harold #10MGM Oil & Gas Inc.ConchoApr 17, 1986———
Dutton Harold #7Texas Concho Operating Co.ConchoMar 11, 1986———
Dutton Harold #9MGM Oil & Gas Inc.ConchoFeb 28, 1986———
Dutton Harold #8MGM Oil & Gas Inc.ConchoDec 17, 1985———

About this data

Field 89118500 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. Nothing is estimated.

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