FIELDS · TEXAS · FIELD 27135600

Eagleville (Eagle Ford Sour)

Field · District 01 · Frio County and 1 more · Eagle Ford Sour in every state →

Eagleville (Eagle Ford Sour) is an RRC field with 3 leases on file reported by 3 operators, mostly in Frio County.

No volume has been reported since April 2018.

Cabot Oil & Gas Corporation holds the most, 2 leases and 93,512 barrels of oil lifetime.

Lifetime, the field has reported 116,097 barrels of oil and 226,819 mcf of gas.

3
leases on file
0
leases reporting volume
3
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
116,097
bbl oil, lifetime · 226,819 Mcf gas

Every well completed in it, searchable →

Reported production by month

12 months through Apr 2026 0 · prior 12 0

05001K20192020202120222023202420252026

Eagleville (Eagle Ford Sour): Oil by month.

Operators

BY LIFETIME OIL ON THEIR LEASES · TOP 2

OperatorLeasesOil, bblGas, McfLast reported
Cabot Oil & Gas Corporation293.5K106KDec 2010
Chesapeake Operating, L.L.C.122.6K120KApr 2018

All 3 leases in Eagleville (Eagle Ford Sour), searchable →

Counties

Latest completions

BY COMPLETION DATE

WellOperatorCountyCompletedTop perf, ftOil, 12 moGas, 12 mo
Arminius Energy Trust #2Javelin Energy Partners Mgmt LLCFrioOct 19, 2010———
Arminius Energy Trust #1Javelin Energy Partners Mgmt LLCFrioSep 2, 2010———
Devine-Nuts #1HChesapeake Operating L.L.C.La SalleApr 25, 2010———
Patrick West #1Javelin Energy Partners Mgmt LLCFrioMar 8, 2010———

About this data

Field 27135600 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, Eagle Ford Sour, is read from the field's name. Nothing is estimated.

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