FIELDS · TEXAS · FIELD 81115063

Sarita ( 2-M)

Field · District 04 · Kenedy County and 1 more

Sarita ( 2-M) is an RRC field with 2 leases on file reported by 2 operators, in Kenedy County.

Exxon Corp. holds the most, 1 lease and 0 barrels of oil lifetime.

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

2
leases on file
0
leases reporting volume
2
operators, all time
0
active wellbores of 12 · 0 operators today
0
bbl oil, 12 months through Apr 2026
0
Mcf gas, same 12 months
0
bbl oil, lifetime · 79,058 Mcf gas

Every well completed in it, searchable →

Operators

BY LIFETIME OIL ON THEIR LEASES · TOP 2

OperatorLeasesOil, bblGas, McfLast reported
Exxon Corp.100—
Exxon Mobil Corporation1079.1KAug 1998

All 2 leases in Sarita ( 2-M), searchable →

Counties

Latest completions

BY COMPLETION DATE

WellOperatorCountyCompletedTop perf, ftOil, 12 moGas, 12 mo
Sarita Field Oil & Gas Unit #17Exxon Corp.KenedyJan 26, 1996———
Sarita Gas Unit No. 7 #3 FExxon Corp.KenedyJan 3, 1984———
Sarita Field Oil & Gas Unit #145 FExxon Mobil CorporationKenedyDec 9, 1982———
Sarita Field Oil & Gas Unit #114Exxon Corp.KenedyFeb 1, 1973———
Sarita Field Oil & Gas Unit #12Exxon Corp.KenedyMar 1, 1972———
Sarita Fld. O. & G. Unit #124 FExxon Corp.KenedyJul 1, 1970———
Sarita Field Oil & Gas Unit #48 FExxon Corp.KenedyDec 1, 1968———
Sarita Field Oil & Gas Unit #11Headington Energy Partners LLCKenedyJul 31, 1967———
9Exxon Corp.HidalgoNov 1, 1953———

About this data

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