LEASES · O-13-18805 · OIL · DISTRICT 09
Furr, Ellis
No volume since Feb 2013Texas Shallow Oil & Gas, LLC · Young County · Camm (Miss.) field
Furr, Ellis is an RRC oil lease (O-13-18805) in Young County operated by Texas Shallow Oil & Gas, LLC, with 2 wells completed on it.
It has reported 11.8K barrels of oil since January 1993, last reporting volume in February 2013 (statewide data runs through April 2026).
No volume was reported in the last 12 months; the last was in February 2013.
9 operators have filed production on it, most recently Texas Shallow Oil & Gas, LLC since January 2017.
- 11.8K
- bbl oil, all reported
- 0
- mcf gas incl. casinghead
- 0
- bbl oil, last 12 reported
- —
- vs the 12 before
- 2
- wells completed on it
- 1.92K
- peak month, bbl (Aug 1996)
PDQ LEASE REPORTS · FIRST JAN 1993 · LAST VOLUME FEB 2013 · 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
Who reported it
Each run of months one operator filed the production report, oldest first.
- Britton Operating, Inc.Jan 1993 → Jul 1995 · 31 mo
- Thompson, Mark P.Aug 1995 → Dec 1995 · 5 mo
- Kas ProductionsJan 1996 → Nov 1998 · 35 mo
- J C Global Enviro Consortium IncDec 1998 → Mar 2003 · 52 mo
- IpactApr 2003 → Jun 2006 · 39 mo
- DJD Drilling CorporationJul 2006 → Oct 2008 · 28 mo
- Dolberry Energy Resources Corp.Nov 2008 → Mar 2013 · 53 mo
- Yohawk Operating, LLCApr 2013 → Dec 2016 · 45 mo
- Texas Shallow Oil & Gas, LLCJan 2017 → Jul 2026 · 115 mo
Wells on the lease
FROM COMPLETION REPORTS · PRODUCTION ABOVE IS THEIR TOTAL
2
wells completed on the lease
- Plugged
- 2
Operates them now
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-18805, documented in the API reference.