WELL · 42-001-31408 · DISTRICT 6

Holland #1

Plugged

Anderson County · Purt W. (Rodessa 10 200) field  · Vertical

Holland #1 (API 42-001-31408) is a plugged well in Anderson County, plugged January 27, 2022, last operated by Southwest Operating Inc.-Tyler.

The RRC has issued one drilling permit, issued April 15, 1983, permitted to 10,800 ft.

It was permitted by Marshall Expl. Inc. and has since transferred to Southwest Operating Inc.-Tyler on the wellbore schedule.

Completion filings report 4 formation tops, including B/Austin Chalk, Georgetown, Glen Rose, B/Massive Anhydrite.

Operator of record

Southwest Operating Inc.-Tyler

Permitted by Marshall Expl. Inc.; the EWA schedule now lists a different operator.

Tyler, TX · P-5 Y, filed Feb 4, 2026 · 63 permits on file · (903) 530-1563

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSouthwest Operating Inc.-Tyler
Production reportsSouthwest Operating, Inc.-Tylerthrough Jul 2018
Latest permitMarshall Expl. Inc.Apr 15, 1983

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

10,800
total depth, ft
1
permits on file
Apr 15, 1983
last permit issued
May 26, 1983
completed
0
cumulative oil, bbl
144K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2022

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
May 26, 1983
Shut in
—
Plugged
Jan 27, 2022

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
Holland G-6-130767Purt,w. (Rodessa 10,200)Southwest Operating, Inc.-Tyler10144KJan 1993 – Jul 2022

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. 1Strago Petroleum CorporationJan 1993 → Jul 1993
  2. 2Buffco Production Inc.Aug 1993 → Jul 2012
  3. 3Southwest Operating, Inc.-TylerOct 2012 → Jul 2018

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
191652-99DrillMarshall Expl. Inc.Apr 15, 1983Apr 15, 1983—10,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-6-130767————

Formation tops

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

FormationMD ftSubsea
B/Austin Chalk5,175-4,572
Georgetown6,690-6,087
Glen RoseGLENROSE8,317-7,714
B/Massive Anhydrite10,200-9,597

Perforations

Perforated and open-hole intervals.

FromToType
10,36710,398Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,17312.25750 S
2.87510,298——
5.510,6508.75500 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 23, 1989Apr 27, 1989—
00Jun 2, 1989——
00Jan 12, 1984Jun 6, 1983—

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