WELL · 42-015-30659 · DISTRICT 3

Herman #1

Y

Austin County · Lake Rd. (Jackson) field · Producing  · Vertical

Herman #1 (API 42-015-30659) is a well in Austin County operated by Bear Creek Energy LLC, completed February 24, 1995 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued September 19, 1994, permitted to 7,500 ft.

It was permitted by Shamrock Oil CO. and has since transferred to Bear Creek Energy LLC on the wellbore schedule.

Completion filings report one formation top, including Jackson.

Its lease has reported 51.2K barrels of oil and 18 mcf of gas since February 1995, last reporting in July 2026.

Operator of record

Bear Creek Energy LLC

Permitted by Shamrock Oil Co.; the EWA schedule now lists a different operator.

Sealy, TX · P-5 Y, filed Jun 4, 2026 · 1 permits on file · (512) 460-9907

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBear Creek Energy LLC
Production reportsBear Creek Energy, LLCthrough Mar 2026
Latest permitShamrock Oil Co.Sep 19, 1994

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

7,500
total depth, ft
2
permits on file
Sep 19, 1994
last permit issued
Feb 24, 1995
completed
51.2K
cumulative oil, bbl
18
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 1995 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Feb 24, 1995
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Herman O-3-22668Lake Rd. (Jackson)Bear Creek Energy, LLC151.2K18Feb 1995 – Jul 2026

Oil, barrels lease total

Last 12 months 926 · prior 12 1,504(-38%)

0100200300202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Shamrock Oil Co.Feb 1995 → Aug 1998
  2. 2HMX Investments, Inc.Mar 1999 → May 2020
  3. 3Bear Creek Energy, LLCSep 2020 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
425978-98DrillShamrock Oil Co.Jan 8, 1996Sep 19, 1994—4,200
425978-99DrillShamrock Oil Co.Jul 18, 1994Sep 19, 1994Jan 10, 19957,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-22668————

Formation tops

As filed on W-2/G-1. Subsea from 165 ft elevation.Download CSV →

FormationMD ftSubsea
Jackson3,350-3,185

Perforations

Perforated and open-hole intervals.

FromToType
3,3703,380Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62550312.2580 S
4.53,5817.875420 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Apr 12, 1995Mar 16, 1995Yes
00Apr 7, 1995——

The source documents

Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.

About this data

Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.

New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease

Developers: this page as JSON is GET /v1/data/wells/01530659, documented in the API reference.