LEASES · O-13-5357 · OIL · DISTRICT 09

Ramming -B-

No volume since Sep 2004

Double E Oil & Gas, L. P. · Wichita County Regular field

Ramming -B- is an RRC oil lease (O-13-5357) in the Wichita County Regular field operated by Double E Oil & Gas, L. P., with one well completed on it.

It has reported 520 barrels of oil and 136 mcf of gas since January 1993, last reporting volume in September 2004 (statewide data runs through April 2026).

No volume was reported in the last 12 months; the last was in September 2004.

2 operators have filed production on it, most recently Double E Oil & Gas, L. P. since October 2004.

520
bbl oil, all reported
136
mcf gas incl. casinghead
0
bbl oil, last 12 reported
—
vs the 12 before
1
wells completed on it
54
peak month, bbl (Apr 2003)

PDQ LEASE REPORTS · FIRST JAN 1993 · LAST VOLUME SEP 2004 · 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

012007200820092010201120122013201420152016

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

012007200820092010201120122013201420152016

Who reported it

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

  1. Oscar Oil CompanyJan 1993 → Sep 2004 · 141 mo
  2. Double E Oil & Gas, L. P.Oct 2004 → Jan 2016 · 136 mo

Wells on the lease

FROM COMPLETION REPORTS · PRODUCTION ABOVE IS THEIR TOTAL

1

wells completed on the lease

Plugged
1

Operates them now

Newest permits

  • — #1—

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-13-5357, documented in the API reference.