LEASES · O-10-24808 · OIL · DISTRICT 08

Sterling "H" Fee

No volume since Mar 2015

Chevron U. S. A. Inc. · Sterling County · Conger (Penn) field

Sterling "H" Fee is an RRC oil lease (O-10-24808) in Sterling County operated by Chevron U. S. A. Inc., with 16 wells completed on it.

It has reported 34.7K barrels of oil and 925K mcf of gas since January 1993, last reporting volume in March 2015 (statewide data runs through April 2026).

No volume was reported in the last 12 months; the last was in March 2015.

2 operators have filed production on it, most recently Chevron U. S. A. Inc. since June 2002.

34.7K
bbl oil, all reported
925K
mcf gas incl. casinghead
0
bbl oil, last 12 reported
—
vs the 12 before
16
wells completed on it
916
peak month, bbl (Mar 1993)

PDQ LEASE REPORTS · FIRST JAN 1993 · LAST VOLUME MAR 2015 · STATEWIDE DATA THROUGH APR 2026

Oil by month

Barrels reported on Form PR for the whole lease. The latest months are revised upward as late reports arrive.

Last 12 months 0 · prior 12 0

0510152007200820092010201120122013201420152016

Gas by month

Gas-well gas plus casinghead gas, mcf. On an oil lease all gas is reported as casinghead. The latest months are revised upward as late reports arrive.

Last 12 months 50 · prior 12 1,318(-96%)

01002003002007200820092010201120122013201420152016

Who reported it

Each run of months one operator filed the production report, oldest first.

  1. Texaco E & P Inc.Jan 1993 → May 2002 · 113 mo
  2. Chevron U. S. A. Inc.Jun 2002 → Feb 2016 · 165 mo

Wells on the lease

FROM COMPLETION REPORTS · PRODUCTION ABOVE IS THEIR TOTAL

16

wells completed on the lease

Not on Schedule
15
Plugged
1

Newest permits

All 16 wells, searchable →

About this data

Monthly oil, gas, and casinghead from the RRC PDQ production dump, which lags the reporting month by two to three months; figures shown through Apr 2026. Wells from completion reports; operator runs from who filed each month's report.

Developers: this page as JSON is GET /v1/data/leases/tx/o-10-24808, documented in the API reference.