FIELDS · TEXAS · FIELD 49245500

Killibrew (Morrow, Lo.)

Field · District 10 · Roberts County · Morrow LO in every state →

Killibrew (Morrow, Lo.) is an RRC field with 5 leases on file reported by 18 operators, in Roberts County.

In the 12 months reported through April 2026 it produced 20,584 mcf of gas, down 30% on the year before, from 1 leases reporting volume.

Choice Exploration, Inc. holds the most, 1 leases and 0 barrels lifetime.

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

5
leases on file
1
leases reporting volume
18
operators, all time
1
active wellbores of 2 · 1 operators today
0
bbl oil, 12 months through Apr 2026
20,584
Mcf gas, same 12 months · −30%
0
bbl oil, lifetime · 2.3M Mcf gas

Every well completed in it, searchable →

Reported production by month

Last 12 months 20,584 · prior 12 29,468(-30%)

02K4K6K2017201820192020202120222023202420252026

Killibrew (Morrow, Lo.): Gas by month.

Operators

BY LIFETIME OIL ON THEIR LEASES · TOP 5

OperatorLeasesOil, bblGas, McfLast reported
Choice Exploration, Inc.10273KMar 2014
Granite Operating Company10185KSep 2011
Merex Resources, Inc.100Feb 1994
Sandlot Oil & Gas LLC101.48MJul 2026
Wildhorse Operating Company10365KJul 2013

All 5 leases in Killibrew (Morrow, Lo.), searchable →

Counties

Latest completions

BY COMPLETION DATE

WellOperatorCountyCompletedTop perf, ftOil, 12 moGas, 12 mo
Killebrew #1Wildhorse Operating CompanyRobertsDec 20, 1980—00
M-S-C #1Sandlot Oil & Gas LLCRobertsApr 28, 1980—00

About this data

Field 49245500 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, Morrow LO, is read from the field's name. Nothing is estimated.

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