FIELDS · 73305260 · DISTRICT 01

Prue Ranch (Olmos A)

Frio 4

Prue Ranch (Olmos A) is an RRC field with 4 leases on file reported by 2 operators, in Frio County.

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

LP Oper, LLC holds the most, 4 leases and 4,479 barrels lifetime.

Lifetime, the field has reported 4,479 barrels of oil and 56,981 mcf of gas, across 1 oil and 3 gas leases.

4
leases on file · 1 oil, 3 gas
2
operators, all time
142
bbl oil, last 12 reported +75%
0
mcf gas, last 12 reported
1
leases reporting volume
4.48K
bbl oil, lifetime · 57K mcf

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

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 0 · prior 12 0

01K2K3K20162017201820192020202120222023202420252026

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 142 · prior 12 81(+75%)

010020020162017201820192020202120222023202420252026

Leases reporting volume

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

Latest month 0 · a year earlier 0

01220162017201820192020202120222023202420252026

Operators

BY LIFETIME OIL ON THEIR LEASES · TOP 1

OperatorLeasesOil, bblGas, mcfLast reported
LP Oper, LLC44.48K57KJul 2026

All 4 leases in Prue Ranch (Olmos A), searchable →

Counties

About this data

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