FIELDS · TEXAS · FIELD 45310500

Jack Grimm (Congl.)

Field · District 8A · Cottle County

Jack Grimm (Congl.) is an RRC field with 2 leases on file reported by 2 operators, in Cottle County.

In the 12 months reported through April 2026 it produced 2,410 barrels of oil, up 3% on the year before, from 1 lease reporting volume.

Burgundy Oil & Gas, Inc. holds the most, 1 lease and 63,980 barrels of oil lifetime.

Lifetime, the field has reported 97,965 barrels of oil and 0 mcf of gas.

2
leases on file
1
leases reporting volume
2
operators, all time
1
active wellbores of 6 · 1 operators today
2,410
bbl oil, 12 months through Apr 2026 · +3%
0
Mcf gas, same 12 months
97,965
bbl oil, lifetime · 0 Mcf gas

Every well completed in it, searchable →

Reported production by month

Last 12 months 2,410 · prior 12 2,346(+3%)

02004006002017201820192020202120222023202420252026

Jack Grimm (Congl.): Oil by month.

Operators

BY LIFETIME OIL ON THEIR LEASES · TOP 2

OperatorLeasesOil, bblGas, McfLast reported
Burgundy Oil & Gas, Inc.164K0Jul 2026
Cholla Petroleum, Inc.134K0Jul 2021

All 2 leases in Jack Grimm (Congl.), searchable →

Counties

Latest completions

BY COMPLETION DATE

WellOperatorCountyCompletedTop perf, ftOil, 12 moGas, 12 mo
Brothers #3Burgundy Oil & Gas Inc.CottleApr 27, 2011—00
Brothers #1DBurgundy Oil & Gas Inc.CottleJul 28, 2008—00
Indianola #1Cholla Petroleum Inc.CottleFeb 8, 2007—00
Brothers A. L. B #2General Atlantic Energy Corp.CottleApr 11, 1979—00
Brothers A. L. #1May Petroleum Inc.CottleDec 20, 1978—00
Brothers A. L. #1Grimm Jack F.CottleJun 16, 1977—00

About this data

Field 45310500 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/45310500, documented in the API reference.