LEASES · O-14-5107 · OIL · DISTRICT 10
Peery, Harold
No volume since Jun 2021High River Res Operating, LLC · Lipscomb County · Peery (Cleveland) field
Peery, Harold is an RRC oil lease (O-14-5107) in Lipscomb County operated by High River Res Operating, LLC, with 6 wells completed on it.
It has reported 61.7K barrels of oil and 563K mcf of gas since January 1993, last reporting volume in June 2021 (statewide data runs through April 2026).
No volume was reported in the last 12 months; the last was in June 2021.
4 operators have filed production on it, most recently High River Res Operating, LLC since December 2025.
- 61.7K
- bbl oil, all reported
- 563K
- mcf gas incl. casinghead
- 0
- bbl oil, last 12 reported
- —
- vs the 12 before
- 6
- wells completed on it
- 2.01K
- peak month, bbl (Mar 2007)
PDQ LEASE REPORTS · FIRST JAN 1993 · LAST VOLUME JUN 2021 · 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
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
Who reported it
Each run of months one operator filed the production report, oldest first.
- Balcones Production CompanyJan 1993 → Oct 1995 · 34 mo
- Texas American Resources CompanyNov 1995 → Aug 2016 · 250 mo
- Quanah Panhandle, LLCSep 2016 → Nov 2025 · 111 mo
- High River Res Operating, LLCDec 2025 → Jul 2026 · 8 mo
Wells on the lease
FROM COMPLETION REPORTS · PRODUCTION ABOVE IS THEIR TOTAL
6
wells completed on the lease
- Not on Schedule
- 3
- Shut IN
- 2
- Plugged
- 1
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-14-5107, documented in the API reference.