LEASES · O-1-18810 · OIL · DISTRICT 01
HKH Allocation #4
ReportingXTO Energy Inc. · Atascosa County · Eagleville (Eagle Ford-1) field
Hkh Allocation #4 is an RRC oil lease (O-1-18810) in Atascosa County operated by Xto Energy Inc., with one well completed on it.
It has reported 205K barrels of oil and 350K mcf of gas since January 2016, last reporting volume in April 2026 (statewide data runs through April 2026).
The last 12 reported months total 4.47K barrels of oil, down 51% on the year before; the lease peaked at 9.92K barrels in November 2016.
- 205K
- bbl oil, all reported
- 350K
- mcf gas incl. casinghead
- 4.47K
- bbl oil, last 12 reported
- -51%
- vs the 12 before
- 1
- wells completed on it
- 9.92K
- peak month, bbl (Nov 2016)
PDQ LEASE REPORTS · FIRST JAN 2016 · 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 4,465 · prior 12 9,095(-51%)
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 749 · prior 12 12,593(-94%)
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.
- XTO Energy Inc.Jan 2016 → Jul 2026 · 127 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-1-18810, documented in the API reference.