FIELDS · TEXAS · FIELD 20740310

Corpus Christi, E. (G-3)

Field · District 04 · Nueces County

Corpus Christi, E. (G-3) is an RRC field with 4 leases on file reported by 5 operators, in Nueces County.

No volume has been reported since July 2022.

White Marlin Operating Co, LLC holds the most, 2 leases and 983,500 mcf of gas lifetime.

Lifetime, the field has reported 89,227 barrels of oil and 983,500 mcf of gas, across 1 oil and 3 gas leases.

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

Every well completed in it, searchable →

Reported production by month

12 months through Apr 2026 0 · prior 12 0

01020302017201820192020202120222023202420252026

Corpus Christi, E. (G-3): Oil by month.

Operators

BY LIFETIME OIL ON THEIR LEASES · TOP 3

OperatorLeasesOil, bblGas, McfLast reported
White Marlin Operating Co, LLC289.2K984KJul 2022
Sabco Oil and Gas Corporation100—
Sabco Operating Company, LLC100—

All 4 leases in Corpus Christi, E. (G-3), searchable →

Counties

Latest completions

BY COMPLETION DATE

WellOperatorCountyCompletedTop perf, ftOil, 12 moGas, 12 mo
TR 54 #4LWhite Marlin Operating Co LLCNuecesJun 17, 2016———
TSL 32973/ TR 55/ #5White Marlin Operating Co LLCNuecesDec 19, 2013———
TSL 33099/ TR54/ #3White Marlin Operating Co LLCNuecesMay 30, 1988———

About this data

Field 20740310 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/20740310, documented in the API reference.