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

Sugg C

No volume since Jun 1997

Chevron Midcontinent, L.P. · Sterling County · Sugg Ranch field

Sugg C is an RRC oil lease (O-10-35818) in Sterling County operated by Chevron Midcontinent, L.P., with one well completed on it.

It has reported 199 barrels of oil and 121 mcf of gas since May 1997, last reporting volume in June 1997 (statewide data runs through April 2026).

No volume was reported in the last 12 months; the last was in June 1997.

3 operators have filed production on it, most recently Chevron Midcontinent, L.P. since April 2006.

199
bbl oil, all reported
121
mcf gas incl. casinghead
0
bbl oil, last 12 reported
—
vs the 12 before
1
wells completed on it
162
peak month, bbl (Jun 1997)

PDQ LEASE REPORTS · FIRST MAY 1997 · LAST VOLUME JUN 1997 · 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

012003200420052006200720082009201020112012

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

012003200420052006200720082009201020112012

Who reported it

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

  1. IP Petroleum Company, Inc.May 1997 → Jan 2001 · 45 mo
  2. Pure Resources, L.P.Feb 2001 → Mar 2006 · 62 mo
  3. Chevron Midcontinent, L.P.Apr 2006 → Feb 2012 · 71 mo

Wells on the lease

FROM COMPLETION REPORTS · PRODUCTION ABOVE IS THEIR TOTAL

1

wells completed on the lease

Plugged
1

Newest permits

All 1 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-35818, documented in the API reference.