FIELDS · TEXAS · FIELD 17550640

Chesterville (3770)

Field · District 03 · Colorado County and 1 more

Chesterville (3770) is an RRC field with 5 leases on file reported by 14 operators, mostly in Austin County.

No volume has been reported since September 2020.

Faulconer, Vernon E., Inc. holds the most, 1 lease and 124,439 mcf of gas lifetime.

Lifetime, the field has reported 0 barrels of oil and 1.1 million mcf of gas.

5
leases on file
0
leases reporting volume
14
operators, all time
0
active wellbores of 8 · 0 operators today
0
bbl oil, 12 months through Apr 2026
0
Mcf gas, same 12 months
0
bbl oil, lifetime · 1.1M Mcf gas

Every well completed in it, searchable →

Operators

BY LIFETIME OIL ON THEIR LEASES · TOP 5

OperatorLeasesOil, bblGas, McfLast reported
Faulconer, Vernon E., Inc.10124KJul 2014
Hilcorp Energy Company100Sep 2020
Indexgeo & Associates, Inc.10311KJul 1996
Senora Resources, Inc.106Aug 2016
Zachry Exploration, LLC10641KJun 2013

All 5 leases in Chesterville (3770), searchable →

Counties

Latest completions

BY COMPLETION DATE

WellOperatorCountyCompletedTop perf, ftOil, 12 moGas, 12 mo
Tulane Gordon Unit #1 CZachry Exploration LLCColoradoSep 13, 2011—00
Hillboldt #2Faulconer Vernon E. Inc.AustinApr 20, 1998—00
Schaer W. #1Senora Resources Inc.AustinMar 4, 1998—00
Best G.U. #1Indexgeo & Associates Inc.AustinAug 9, 1993—00
Chesterville Unit #4Mobil Producing TX. & N.M. Inc.ColoradoJun 3, 1988—00
Chesterville Unit #1Samson Lone Star LPColoradoSep 4, 1985—00
Chesterville Unit #8Mobil Producing TX. & N.M. Inc.ColoradoNov 21, 1980—00

About this data

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

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