WELL · 42-405-30319 · DISTRICT 6

Red River 35 #1

Y

San Augustine County · Carthage (Haynesville Shale) field · Producing  · Horizontal

Red River 35 #1 (API 42-405-30319) is a horizontal well in San Augustine County operated by Exco Operating Company LP, completed August 6, 2010 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued February 4, 2010, permitted to 15,000 ft.

Completion filings report 4 formation tops, including Massive Anhydrite (marker), James Lime, Travis Peak, Bossier.

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

Operator of record

Exco Operating Company LP

Dallas, TX · P-5 Y, filed May 4, 2026 · 515 permits on file · (888) 788-3781

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleExco Operating Company LP
Production reportsExco Operating Company, LPthrough Apr 2026
Latest permitCommon Resources L.L.C.Feb 4, 2010

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

15,000
total depth, ft
2
permits on file
Feb 4, 2010
last permit issued
Aug 6, 2010
completed
0
cumulative oil, bbl
3.22M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2010 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 6, 2010
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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
Red River 35 G-6-258972Carthage (Haynesville Shale)Exco Operating Company, LP103.22MAug 2010 – Jul 2026

Gas, mcf lease total

Last 12 months 28,941 · prior 12 31,884(-9%)

02K4K6K202420252026

Chain of custody

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

  1. 1Exco Operating Company, LPAug 2010 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
690613-98DrillExco Operating Company, LPJan 26, 2011Feb 4, 2010Feb 11, 201015,000
690613-99DrillCommon Resources L.L.C.Feb 1, 2010Feb 4, 2010Feb 11, 201015,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-6-258972————

Formation tops

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

FormationMD ftSubsea
Massive Anhydrite (marker)MASSIVE ANHYDRITE6,615-6,250
James Lime7,318-6,953
Travis Peak8,389-8,024
Bossier11,858-11,493

Perforations

Perforated and open-hole intervals.

FromToType
13,34717,429Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3752,31217.51,658 S
5.511,6256.75705 S
7.62511,9439.875520 S
517,5306.75705 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
00Apr 8, 2012Nov 17, 2011—
00Feb 22, 2011Sep 27, 2010Yes

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