WELL · 42-021-31326 · DISTRICT 3

Steinbach G #B 2

Y

Bastrop County · Serbin (Taylor Sand) field · Temp Abandoned  · Vertical

Steinbach G #B 2 (API 42-021-31326) is a well in Bastrop County operated by Digital Operating Company LLC, completed April 3, 1990 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued December 29, 1989, permitted to 5,500 ft.

It was permitted by Melton Energy Inc. and has since transferred to Digital Operating Company LLC on the wellbore schedule.

Completion filings report one formation top, including Taylor.

No lease production has been reported under this well’s leases.

Operator of record

Digital Operating Company LLC

Permitted by Melton Energy Inc.; the EWA schedule now lists a different operator.

Boerne, TX · P-5 Y, filed Aug 4, 2025 · (800) 671-8652

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDigital Operating Company LLC
Production reportsTrivista Operating LLCthrough Oct 2020
Latest permitGeotech Energy Corp.Dec 29, 1989

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

5,500
total depth, ft
2
permits on file
Dec 29, 1989
last permit issued
Apr 3, 1990
completed
0
cumulative oil, bbl
164K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 3, 1990
Shut in
—
Plugged
—

Operator's P-5 on the schedule: H

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
Steinbach G G-3-134502Serbin (Taylor Sand)Digital Operating Company LLC10164KJan 1993 – Jul 2026

No volumes reported on these leases in the last three years.

Chain of custody

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

  1. 1Melton, Joe, Drlg. Co., Inc.Jan 1993 → Sep 1998
  2. 2Texas Vanguard Oil CompanyOct 1998 → Sep 2013
  3. 3Trivista Operating LLCOct 2013 → Oct 2020

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
368123-98DrillMelton Energy Inc.May 16, 1990Dec 29, 1989—5,500
368123-99DrillGeotech Energy Corp.Dec 29, 1989Dec 29, 1989—5,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-134502————

Formation tops

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

FormationMD ftSubsea
TaylorTAYLOR SAND4,980-4,560

Perforations

Perforated and open-hole intervals.

FromToType
4,9825,012Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62555612.25235 S
4.55,1817.8751,150 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
00Jun 8, 1990May 1, 1990Yes
00Jun 1, 1990——

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/02131326, documented in the API reference.