WELL · 42-497-35431 · DISTRICT 9

Stevens Gas Unit #7

Plugged

Wise County · Newark East (Barnett Shale) field  · Vertical

Stevens Gas Unit #7 (API 42-497-35431) is a plugged well in Wise County, plugged February 24, 2017, last operated by Rosehill Operating Company LLC.

The RRC has issued one drilling permit (amended once), issued October 23, 2003, permitted to 8,500 ft.

It was permitted by Tema Oil And Gas Company and has since transferred to Rosehill Operating Company LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Marble Falls, Barnett, Forrestburg.

Operator of record

Rosehill Operating Company LLC

Permitted by Tema Oil and Gas Company; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Inactive (I)
P-5 last filed
May 21, 2021
Permits on file
169
Phone
(281) 675-3400

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleRosehill Operating Company LLC
Production reportsTema Oil and Gas Companythrough Feb 2014
Latest permitTema Oil and Gas CompanyOct 23, 2003

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

8,500
total depth, ft
2
permits on file
Oct 23, 2003
last permit issued
Apr 7, 2004
completed
0
cumulative oil, bbl
238K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2004 THROUGH Mar 2018

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Apr 7, 2004
Shut in
—
Plugged
Feb 24, 2017

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
Stevens Gas Unit G-13-201311Newark, East (Barnett Shale)Rosehill Operating Company, LLC10238KApr 2004 – Mar 2018

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. 1Tema Oil and Gas CompanyApr 2004 → Feb 2014

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
537854-98DrillTema Oil and Gas CompanyJan 14, 2004Oct 23, 2003Jan 21, 20048,500
537854-99DrillTema Oil and Gas CompanyOct 23, 2003Oct 23, 2003—8,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-13-201311————

Formation tops

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

FormationMD ftSubsea
Marble Falls6,723-5,778
BarnettUPPER BARNETT7,025-6,080
Forrestburg7,115-6,170
BarnettLOWER BARNETT7,326-6,381

Perforations

Perforated and open-hole intervals.

FromToType
7,3307,562Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,01412.25500 S
5.57,5967.875220 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
00Jul 15, 2004May 5, 2004Yes
00Jun 2, 2004——

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