WELL · 42-041-31854 · DISTRICT 3

Taplin #1

Plugged

Brazos County · Kurten (Buda) field  · Horizontal

Taplin #1 (API 42-041-31854) is a plugged horizontal well in Brazos County, plugged August 29, 2018, last operated by Ogden Resources Corporation.

The RRC has issued one drilling permit (amended once), issued April 18, 1995, permitted to 12,466 ft.

Completion filings report 2 formation tops, including Austin Chalk, Kurten(Buda).

Its 2 leases have reported 114K barrels of oil and 262K mcf of gas since July 1995, last reporting in August 2019. The leases carry 3 wells, so these are lease totals, not this well alone.

Operator of record

Ogden Resources Corporation

Bryan, TX · P-5 Active, filed Jan 22, 2026 · 64 permits on file · (979) 776-2704

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOgden Resources Corporation
Production reportsOgden Resources Corporationthrough Oct 2018
Latest permitOgden Resources CorporationApr 18, 1995
12,466
total depth, ft
2
permits on file
Apr 18, 1995
last permit issued
Sep 22, 1995
completed
114K
cumulative oil, bbl
262K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 1995 THROUGH Aug 2019

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 22, 1995
Shut in
—
Plugged
Aug 29, 2018

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 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Taplin O-3-22764Giddings (Austin Chalk-3)Ogden Resources Corporation293K227KJul 1995 – Aug 2019
Taplin O-3-22792Kurten (Buda)Ogden Resources Corporation120.9K34.6KSep 1995 – Mar 1996

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. 1Ogden Resources CorporationJul 1995 → Oct 2018
  2. 2Ogden Resources, Ltd.Feb 2005 → Feb 2009

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
434906-98DrillOgden Resources CorporationJun 7, 1995Apr 18, 1995—12,466
434906-99DrillOgden Resources CorporationApr 14, 1995Apr 18, 1995Jun 9, 199512,123

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-22764————
—— O-3-22764————
—— O-3-22792————

Formation tops

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

FormationMD ftSubsea
Austin Chalk7,909-7,599
Kurten(buda)8,930-8,620

Perforations

Perforated and open-hole intervals.

FromToType
8,24011,307Perforated
8,93011,990Perforated
8,96011,990Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.751,90514.75875 S
7.6258,8649.875380 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
00Nov 7, 1995Oct 5, 1995Yes
00Oct 20, 1995Aug 24, 1995Yes
00Oct 20, 1995——
00Sep 25, 1995Aug 24, 1995Yes
00Sep 6, 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/04131854, documented in the API reference.