FIELDS · TEXAS · FIELD 94082790

Volpe (6060)

Field · District 04 · Zapata County

Volpe (6060) is an RRC field with 5 leases on file reported by 7 operators, in Zapata County.

No volume has been reported since April 2025.

EOG Resources, Inc. holds the most, 2 leases and 1.5 million mcf of gas lifetime.

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

5
leases on file
0
leases reporting volume
7
operators, all time
0
active wellbores of 6 · 0 operators today
0
bbl oil, 12 months through Apr 2026
0
Mcf gas, same 12 months
0
bbl oil, lifetime · 6.3M Mcf gas

Every well completed in it, searchable →

Reported production by month

Last 12 months 0 · prior 12 3,721(-100%)

010K20K30K2017201820192020202120222023202420252026

Volpe (6060): Gas by month.

Operators

BY LIFETIME OIL ON THEIR LEASES · TOP 4

OperatorLeasesOil, bblGas, McfLast reported
EOG Resources, Inc.201.5MAug 2006
Chesapeake Operating, Inc.1025.4KSep 2011
Enron Oil & Gas Company10188KAug 1996
Hurd Enterprises, Ltd.104.53MApr 2025

All 5 leases in Volpe (6060), searchable →

Counties

Latest completions

BY COMPLETION DATE

WellOperatorCountyCompletedTop perf, ftOil, 12 moGas, 12 mo
Vela Adrian #2Hurd Enterprises Ltd.ZapataDec 3, 2024—00
Vela #2Chesapeake Operating Inc.ZapataDec 22, 2003—00
Garcia Salvador G #20Southern Tejas Asset Group LLCZapataJun 1, 2000—00
Garcia Salvador G #16Southern Tejas Asset Group LLCZapataNov 9, 1995—00
Garcia Salvador F #17EOG Resources Inc.ZapataJun 3, 1988—00
Vela Emiliano #1Pennzoil Exploration & Prod. Co.ZapataSep 25, 1983—00

About this data

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

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