FIELDS · TEXAS · FIELD 1515666

Alice, Deep (Yegua)

Field · District 04 · Jim Wells County · Yegua in every state →

Alice, Deep (Yegua) is an RRC field with 3 leases on file reported by 4 operators, in Jim Wells County.

No volume has been reported since September 2024.

Cimarron Engineering, LLC holds the most, 1 lease and 225 mcf of gas lifetime.

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

3
leases on file
0
leases reporting volume
4
operators, all time
0
active wellbores of 5 · 0 operators today
0
bbl oil, 12 months through Apr 2026
0
Mcf gas, same 12 months
0
bbl oil, lifetime · 225 Mcf gas

Every well completed in it, searchable →

Reported production by month

12 months through Apr 2026 0

010020030020252026

Alice, Deep (Yegua): Gas by month.

Operators

BY LIFETIME OIL ON THEIR LEASES · TOP 3

OperatorLeasesOil, bblGas, McfLast reported
Cimarron Engineering, LLC10225Sep 2024
Noble Energy Inc100—
Progas Properties, Inc.100—

All 3 leases in Alice, Deep (Yegua), searchable →

Counties

Latest completions

BY COMPLETION DATE

WellOperatorCountyCompletedTop perf, ftOil, 12 moGas, 12 mo
Cook #1Cimarron Engineering LLCJim WellsMar 9, 2024———
Hunter R.J. #1Noble Energy IncJim WellsApr 23, 2007———
Stout-Martens Unit #1Progas Properties Inc.Jim WellsAug 4, 1982———
Knox #1Durst Oil CompanyJim WellsOct 24, 1981———
Goldapp #1Durst Oil CompanyJim WellsJun 26, 1980———

About this data

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

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