LEASES · O-2-9118 · OIL · DISTRICT 02
Bolland Ranch
ReportingTare Resources, LLC · Live Oak County · Bolland Ranch (Hockley) field
Bolland Ranch is an RRC oil lease (O-2-9118) in Live Oak County operated by Tare Resources, LLC, with one well completed on it.
It has reported 27.1K barrels of oil since June 2006, last reporting volume in April 2026 (statewide data runs through April 2026).
The last 12 reported months total 892 barrels of oil, down 42% on the year before; the lease peaked at 411 barrels in August 2006.
4 operators have filed production on it, most recently Tare Resources, LLC since December 2018.
- 27.1K
- bbl oil, all reported
- 0
- mcf gas incl. casinghead
- 892
- bbl oil, last 12 reported
- -42%
- vs the 12 before
- 1
- wells completed on it
- 411
- peak month, bbl (Aug 2006)
PDQ LEASE REPORTS · FIRST JUN 2006 · LAST VOLUME APR 2026 · 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 892 · prior 12 1,546(-42%)
Decline curve
None shown. Petrora fits an Arps curve only when the last ten years of oil reports follow one decline closely enough to project (R² of 0.7 or better over at least a year since the peak). This lease's recent history does not, so a projection would be a guess dressed as a number.
Who reported it
Each run of months one operator filed the production report, oldest first.
- Double Play Oil & Gas, IncJun 2006 → Mar 2011 · 58 mo
- Choice Exploration, Inc.Apr 2011 → Oct 2012 · 19 mo
- Welder Exploration & Prod., Inc.Nov 2012 → Nov 2018 · 73 mo
- Tare Resources, LLCDec 2018 → Jul 2026 · 92 mo
Wells on the lease
FROM COMPLETION REPORTS · PRODUCTION ABOVE IS THEIR TOTAL
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-2-9118, documented in the API reference.