FIELDS · TEXAS · FIELD 90536430

Tom Oconnor, N. (5150)

Field · District 02 · Refugio County

Tom Oconnor, N. (5150) is an RRC field with 1 lease on file reported by 1 operator, in Refugio County.

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

Hilcorp Energy Company holds the most, 1 lease and 83,270 barrels of oil lifetime.

Lifetime, the field has reported 83,270 barrels of oil and 21,765 mcf of gas.

1
leases on file
1
leases reporting volume
1
operators, all time
1
active wellbores of 4 · 1 operators today
2,577
bbl oil, 12 months through Apr 2026 · −28%
99
Mcf gas, same 12 months · −63%
83,270
bbl oil, lifetime · 21,765 Mcf gas

Every well completed in it, searchable →

Reported production by month

12 months through Apr 2026 2,577 · prior 12 3,567(-28%)

05001K2017201820192020202120222023202420252026

Tom Oconnor, N. (5150): Oil by month.

Operators

BY LIFETIME OIL ON THEIR LEASES · TOP 1

OperatorLeasesOil, bblGas, McfLast reported
Hilcorp Energy Company183.3K21.8KApr 2026

All 1 leases in Tom Oconnor, N. (5150), searchable →

Counties

Latest completions

BY COMPLETION DATE

WellOperatorCountyCompletedTop perf, ftOil, 12 moGas, 12 mo
Heard Claude E. et al #44Hilcorp Energy CompanyRefugioAug 13, 2020———
Heard Claude E. et al #39Hilcorp Energy CompanyRefugioNov 28, 2011———
Heard Claude E. et al #24Hilcorp Energy CompanyRefugioJun 12, 2009———

About this data

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

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