TEXAS · WELLS · RUSK COUNTY · VIPER #1 LEASE · API 42-401-34668 · DISTRICT 06

Viper #1 #6

Plugged

Rusk County · Minden (Cotton Valley Cons.) field  · Vertical

Fields on the latest permit · any of 2
Minden (Cotton Valley Cons.) · Minden (Travis Peak Cons.)
Not one formation; the well must be completed in one of them, and no target formation is stated.

Viper #1 #6 (API 42-401-34668) is a plugged well in Rusk County, plugged June 25, 2026, last operated by Sabine Energy Inc..

The RRC has issued one drilling permit, issued February 28, 2008, permitted to 12,100 ft.

It was permitted by El Paso E & P Company, L. P. and has since transferred to Sabine Energy Inc. on the wellbore schedule.

Completion filings report 5 formation tops, including Rodessa, Travis Peak, Cotton Valley, Taylor.

Its lease has reported 1.25K barrels of oil and 422K mcf of gas since October 2008, with no volume in the three years through April 2026.

Operator of record

Sabine Energy Inc.

Permitted by El Paso E & P Company, L. P.; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Feb 6, 2026
Permits on file
66
Phone
(832) 242-9600

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSabine Energy Inc.
Production reportsSabine Energy Inc.through Oct 2022
Latest permitEl Paso E & P Company, L. P.Feb 28, 2008

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

12,100
total depth, ft
1
permits on file
Feb 28, 2008
last permit issued
Oct 18, 2008
completed
1.25K
cumulative oil, bbl
422K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · OCT 2008 THROUGH OCT 2022

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 18, 2008
Shut in
—
Plugged
Jun 25, 2026

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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

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
Viper #1 G-6-243215Minden (Cotton Valley Cons.)Sabine Energy Inc.11.25K422KOct 2008 – Oct 2022

No volumes reported on these leases in the last three years.

Wells named Viper #1

Sabine Energy Inc.'s other wells filed under this lease name in Rusk County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Chain of custody

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

  1. 1El Paso E & P Company, L. P.Oct 2008 → Oct 2011
  2. 2NFR Energy, LLCNov 2011 → Jan 2013
  3. 3Sabine Oil & Gas LLCFeb 2013 → Mar 2015
  4. 4Sabine Oil & Gas CorporationApr 2015 → Oct 2022

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
655745-99DrillEl Paso E & P Company, L. P.Feb 21, 2008Feb 28, 2008Aug 31, 200812,100

Completions

CompletedLeaseFieldOperatorStatusDepth
Oct 18, 2008Viper #1 G-6-243215Minden (Cotton Valley Cons.)Sabine Energy Inc.Plugged—

Formation tops

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

FormationMD ftSubsea
Rodessa6,377-5,997
Travis Peak7,287-6,907
Cotton Valley9,177-8,797
Taylor10,442-10,062
Bossier10,742-10,362

Perforations

Perforated and open-hole intervals.

FromToType
9,5369,780Perforated
9,87210,290Perforated
10,50210,668Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,22712.25430 S
4.510,9258.751,300 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Jan 10, 2009Nov 19, 2008Yes
00Dec 19, 2008——

Well logs

1 log loaded from the RRC's log index, the latest received Oct 11, 2011. Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
RESISTIVITYSpans Rodessa, Travis Peak, Cotton Valley, Taylor, BossierTIFF1,222 to 10,930Oct 11, 2011run Sep 15, 20080.74

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it.

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