LEASES · O-4-8322 · OIL · DISTRICT 04

Hahl-Burch B-3

No volume since Jan 1996

HMT Pipeline Company, Inc. · Duval County · Govt. Wells, N. ( Mirando, N) field

Hahl-Burch B-3 is an RRC oil lease (O-4-8322) in Duval County operated by Hmt Pipeline Company, Inc., with one well completed on it.

It has reported 1.07K barrels of oil and 4 mcf of gas since January 1993, last reporting volume in January 1996 (statewide data runs through April 2026).

No volume was reported in the last 12 months; the last was in January 1996.

2 operators have filed production on it, most recently Hmt Pipeline Company, Inc. since November 1996.

1.07K
bbl oil, all reported
4
mcf gas incl. casinghead
0
bbl oil, last 12 reported
—
vs the 12 before
1
wells completed on it
161
peak month, bbl (Nov 1994)

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

012017201820192020202120222023202420252026

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

012017201820192020202120222023202420252026

Who reported it

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

  1. Stinger Oil & Gas Inc.Jan 1993 → Oct 1996 · 46 mo
  2. HMT Pipeline Company, Inc.Nov 1996 → Jul 2026 · 357 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

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-4-8322, documented in the API reference.