TEXAS · WELLS · STEPHENS COUNTY · SWENSON "55" LEASE · API 42-429-33740 · DISTRICT 6E

Swenson 55 #1

Y

Stephens County · Taylor-Wilson (Duffer) field · Producing  · Vertical

Swenson 55 #1 (API 42-429-33740) is a well in Stephens County operated by Petex, completed May 3, 2005 and listed as producing on the RRC schedule.

The RRC has issued 2 drilling permits between 1983 and 2005, permitted to 4,239 ft.

It was permitted by Mcclymond, Ltd. and has since transferred to Petex on the wellbore schedule.

Completion filings report 2 formation tops, including Caddo, Duffer.

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

Operator of record

Petex

Permitted by McClymond, Ltd.; the EWA schedule now lists a different operator.

Based in
Breckenridge, TX
P-5 status
Active – Extension (X)
P-5 last filed
Jun 24, 2026
Permits on file
124
Phone
(254) 559-5453

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePetex
Production reportsPetexthrough Apr 2026
Latest permitMcClymond, Ltd.Feb 28, 2005

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

4,239
total depth, ft
2
permits on file
Feb 28, 2005
last permit issued
May 3, 2005
completed
0
cumulative oil, bbl
221K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2005 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 3, 2005
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active – Extension (X)

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
Swenson "55" G-8-209992Taylor-Wilson (Duffer)Petex10221KMay 2005 – Jul 2026

Gas, mcf lease total

Last 12 months 857 · prior 12 469(+83%)

0200400600202420252026

Chain of custody

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

  1. 1McClymond, Ltd.May 2005 → Dec 2009
  2. 2PetexJan 2010 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
558182-99ReenterMcClymond, Ltd.Feb 24, 2005Feb 28, 2005Apr 22, 20054,500
202012-99DrillTXO Production Corp.Jul 19, 1983Jul 19, 1983Aug 8, 19834,500

Completions

CompletedLeaseFieldOperatorStatusDepth
May 3, 2005Swenson 55 G-8-209992Taylor-Wilson (Duffer)PetexProducing4,239

Formation tops

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

FormationMD ftSubsea
Caddo3,305-1,932
Duffer4,050-2,677

Perforations

Perforated and open-hole intervals.

FromToType
4,0504,062Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62521311120 S
4.54,2257.875200 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
00Oct 17, 2005Jun 16, 2005Yes
00Aug 11, 2005——

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