FIELDS · 72240500 · DISTRICT 03

Pond Gully (Frio 8110)

Jefferson 2

Pond Gully (Frio 8110) is an RRC field with 2 leases on file reported by 2 operators, in Jefferson County.

In the 12 months reported through April 2026 it produced 63 barrels of oil, down 100% on the year before, from 1 leases reporting volume.

Hilcorp Engy Co holds the most, 2 leases and 588,018 barrels lifetime.

Lifetime, the field has reported 588,018 barrels of oil and 285,485 mcf of gas.

2
leases on file
2
operators, all time
63
bbl oil, last 12 reported -100%
93
mcf gas, last 12 reported -99%
1
leases reporting volume
588K
bbl oil, lifetime · 285K mcf

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Oil by month

TEN YEARS · EVERY LEASE IN THE FIELD

Barrels reported on Form PR across the field's leases. The latest months are revised upward as late reports arrive.

Last 12 months 63 · prior 12 13,858(-100%)

05K10K20162017201820192020202120222023202420252026

Gas by month

TEN YEARS · EVERY LEASE IN THE FIELD

Gas-well gas plus casinghead, mcf, across the field's leases. The latest months are revised upward as late reports arrive.

Last 12 months 93 · prior 12 7,706(-99%)

02K4K20162017201820192020202120222023202420252026

Leases reporting volume

How many of the field's leases reported any oil or gas each month: the field's active footprint.

Latest month 1 · a year earlier 0

01220162017201820192020202120222023202420252026

Operators

BY LIFETIME OIL ON THEIR LEASES · TOP 1

OperatorLeasesOil, bblGas, mcfLast reported
Hilcorp Engy Co2588K285KJul 2026

All 2 leases in Pond Gully (Frio 8110), searchable →

Counties

About this data

Field 72240500 from RRC PDQ lease reports: lifetime totals and lease and operator counts from the field summary; the monthly series summed nightly from every lease report naming the field, cut at the statewide reported-through month. Counties from the wells completed on each lease.

New to these records? how production is reported

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