OPERATORS · TEXAS · P-5 NUMBER 41863 · MEDINA COUNTY

B.T.H. Investments in Medina County

One operator, one county: its permits, wells of record, formations, and leases here, with the rest of the county and the rest of the operator one click away.

B.T.H. Investments has 10 drilling permits on file in Medina County, the first issued in 1981 and the latest on June 30, 1981.

None were issued in the last twelve months.

It is not operator of record on any well in the county on the current wellbore schedule.

0
permits, 12 months
10
permits, all time since 1981
—
horizontal, 12 months
—
ft average depth, 12 months
0
wells of record
0
producing · 0 shut in · 0 injection

Permits issued by month

LAST FIVE YEARS · MEDINA ONLY

Last 12 months 0 · prior 12 0

0120222023202420252026

Latest permits here

IssuedLease / wellTypeDepth
Jun 30, 1981Mann, Augusta #60 123169Drill300
Jun 30, 1981Mann, Augusta #59 123168Drill300
Jun 30, 1981Mann, Augusta #58 123166Drill300
Jun 30, 1981Mann, Augusta #56 123165Drill300
Jun 30, 1981Mann, Augusta #55 123163Drill300
Jun 30, 1981Mann, Augusta #54 123161Drill300
Jun 30, 1981Mann, Augusta #53 123160Drill300
Jun 30, 1981Mann, Augusta #52 123159Drill300
Jun 30, 1981Mann, Augusta #51 123157Drill300
Jun 30, 1981Mann, Augusta #50 123155Drill300

All 10 permits in Medina County, searchable → ·  Wells of record here →

Permit types and formations

Permit types

Drill
0 / 10

12 MONTHS / ALL TIME

Formations reported

No completion tops on file for its wells here.

Leases it reports here

No leases with wells completed in this county carry this operator's production reports.

All leases it reports → ·  Other operators in Medina County →

About this data

Permits from the RRC OGA049M master and daily daf420 files; wells of record and status from the EWA wellbore schedule, weekly; formations from the dbf900 wellbore file; leases from PDQ lease reports, placed in the county by the wells completed on them.

Developers: this page as JSON is GET /v1/data/operators/tx/41863/counties/medina, documented in the API reference.