FIELDS · TEXAS · FIELD 12464085

Brownever (Dean)

Field · District 7C · Irion County · Dean in every state →

Brownever (Dean) is an RRC field with 5 leases on file reported by 6 operators, in Irion County.

In the 12 months reported through April 2026 it produced 4,195 mcf of gas, down 24% on the year before, from 2 leases reporting volume.

Triple Crown Resources, LLC holds the most, 2 leases and 93,012 barrels lifetime.

Lifetime, the field has reported 107,096 barrels of oil and 1.4 million mcf of gas, across 4 oil and 1 gas leases.

5
leases on file · 4 oil, 1 gas
2
leases reporting volume
6
operators, all time
0
active wellbores of 3 · 0 operators today
530
bbl oil, 12 months through Apr 2026 · −19%
4,195
Mcf gas, same 12 months · −24%
107,096
bbl oil, lifetime · 1.4M Mcf gas

Every well completed in it, searchable →

Reported production by month

Last 12 months 530 · prior 12 655(-19%)

02004002017201820192020202120222023202420252026

Brownever (Dean): Oil by month.

Operators

BY LIFETIME OIL ON THEIR LEASES · TOP 3

OperatorLeasesOil, bblGas, McfLast reported
Triple Crown Resources, LLC293K760KJul 2026
COG Operating LLC29.02K604KMay 2016
Ganador Operating, LLC15.07K30.9KJun 2024

All 5 leases in Brownever (Dean), searchable →

Counties

Latest completions

BY COMPLETION DATE

WellOperatorCountyCompletedTop perf, ftOil, 12 moGas, 12 mo
Sugg 29 NE #5COG Operating LLCIrionAug 26, 2010—00
Sugg 30 NE #5Triple Crown Resources LLCIrionJul 12, 2010—00
Sugg 3060 #1COG Operating LLCIrionDec 10, 2002—00

About this data

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

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