WELL · 42-077-33748 · DISTRICT 9

Sanzenbacher #1

N

Clay County · Clay County Regular field  · Vertical

Sanzenbacher #1 (API 42-077-33748) is a well in Clay County operated by Golden Resources Corporation, completed July 17, 1985.

The RRC has issued one drilling permit, issued April 12, 1985, permitted to 6,000 ft.

Completion filings report 4 formation tops, including Gryson, Smithwick, Laddo, Atoka.

Its 2 leases have reported 75.4K barrels of oil and 113K mcf of gas since January 1993, last reporting in July 2026. The leases carry 7 wells, so these are lease totals, not this well alone.

Operator of record

Golden Resources Corporation

Dallas, TX · P-5 Y, filed Feb 5, 1999 · 26 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleGolden Resources Corporation
Production reportsBonfire Operating LLCthrough Jun 2025
Latest permitGolden Resources CorporationApr 12, 1985

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

6,000
total depth, ft
1
permits on file
Apr 12, 1985
last permit issued
Jul 17, 1985
completed
75.4K
cumulative oil, bbl
113K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 17, 1985
Shut in
—
Plugged
—

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 2 leases this well is completed on; they carry 7 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Fields Waterflood Unit O-13-28508Clay County RegularBonfire Operating LLC675.2K112KFeb 1993 – Jul 2026
Sanzenbacher O-13-25526Clay County RegularGolden Resources Corporation1153774Jan 1993 – May 1993

Oil, barrels lease total

Last 12 months 12 · prior 12 568(-98%)

050100150202420252026

Chain of custody

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

  1. 1Golden Resources CorporationJan 1993 → Dec 1998
  2. 2Golden Resources, LLCJan 1999 → Nov 2006
  3. 3Golden Resources, L.L.C.Dec 2006 → Apr 2015
  4. 4Bonfire Operating LLCJan 2017 → Jun 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
272059-99DrillGolden Resources CorporationApr 12, 1985Apr 12, 1985May 3, 19856,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-25526————
—— O-13-28508————

Formation tops

As filed on W-2/G-1. Download CSV →

FormationMD ft
Gryson4,852
Smithwick5,664
Laddo5,804
Atoka5,925

Perforations

Perforated and open-hole intervals.

FromToType
5,8105,820Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62533312.25225 S
4.55,9067.875250 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
00Mar 5, 1993Aug 13, 1985—
00Sep 9, 1985Aug 13, 1985—
00Aug 31, 1985——

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