FIELDS · TEXAS · FIELD 49038142

Kermit (Fusselman)

Field · District 08 · Winkler County · Fusselman in every state →

Kermit (Fusselman) is an RRC field with 27 leases on file reported by 21 operators, in Winkler County.

No volume has been reported since July 2026.

Discovery Operating, Inc. holds the most, 2 leases and 231,748 mcf of gas lifetime.

Lifetime, the field has reported 28,961 barrels of oil and 2.4 million mcf of gas, across 5 oil and 22 gas leases.

27
leases on file · 5 oil, 22 gas
0
leases reporting volume
21
operators, all time
1
active wellbores of 41 · 1 operators today
0
bbl oil, 12 months through Apr 2026
0
Mcf gas, same 12 months
28,961
bbl oil, lifetime · 2.4M Mcf gas

Every well completed in it, searchable →

Reported production by month

Last 12 months 0 · prior 12 0

02040602017201820192020202120222023202420252026

Kermit (Fusselman): Oil by month.

Operators

BY LIFETIME OIL ON THEIR LEASES · TOP 11

OperatorLeasesOil, bblGas, McfLast reported
Discovery Operating, Inc.215.2K232KJul 2026
Mineral Technologies, Inc.19.12K56.6KJul 2026
Cimarex Energy Co. of Colorado22.41K67.1KApr 2012
Parker & Parsley Development L.P12.22K56.1KJun 1996
Devon Energy Production Co, L.P.110570KFeb 2013
Pennzoil Exploration & Prod. Co.400Mar 1998
Texaco E & P Inc.20516May 1994
Meco IV, LLC101.43MAug 2017
Hilcorp Energy Company100Jul 2026
Apache Corporation100Jul 2011
Midpar L.P.1013.9KAug 1994

All 27 leases in Kermit (Fusselman), searchable →

Counties

Latest completions

BY COMPLETION DATE

About this data

Field 49038142 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. The formation, Fusselman, is read from the field's name. Nothing is estimated.

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