WELL · 42-431-32755 · DISTRICT 8

Stewart #901

Plugged

Sterling County  · Vertical

Stewart #901 (API 42-431-32755) is a plugged well in Sterling County, plugged August 22, 1994, last operated by Steller Energy & Investment Corp.

The RRC has issued 2 drilling permits between 1994 and 2009, permitted to 9,000 ft.

Completion filings report 6 formation tops, including Coleman Junction, Triple M Marker, Cisco, Pennsylvanian.

Its lease has reported 18.7K barrels of oil and 163K mcf of gas since August 2009, last reporting in July 2026.

Operator of record

Steller Energy & Investment Corp

Based in
Plano, TX
P-5 status
Inactive (I)
P-5 last filed
Feb 11, 2020
Permits on file
160
Phone
(972) 673-1215

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsTrigeo Energy, LLCthrough Jul 2024
Latest permitSteller Energy & Investment CorpAug 11, 2009
9,000
total depth, ft
2
permits on file
Aug 11, 2009
last permit issued
—
completed
18.7K
cumulative oil, bbl
163K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2009 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
Aug 22, 1994

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
Stewart 9 O-10-39718Spraberry (Trend Area)Trigeo Energy, LLC118.7K163KAug 2009 – Jul 2026

Gas, mcf lease total

Last 12 months 0 · prior 12 1,463(-100%)

05001K202420252026

Oil, barrels lease total

Last 12 months 0 · prior 12 0

0102030202420252026

Chain of custody

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

  1. 1Steller Energy & Investment CorpAug 2009 → Apr 2016
  2. 2Atoka Operating Permian, LLCMay 2016 → May 2023
  3. 3Trigeo Energy, LLCJun 2023 → Jan 2024

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
683615-99ReenterSteller Energy & Investment CorpJul 29, 2009Aug 11, 2009Aug 11, 20099,000
424755-99DrillAdkins, R. L. Corp.Jun 10, 1994Jun 16, 1994Aug 4, 19948,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-39718————

Formation tops

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

FormationMD ftSubsea
Coleman Junction4,046-1,508
Triple M Marker7,249-4,711
CiscoCISCO MARKER7,533-4,995
PennsylvanianPENN SHALE MARKER8,449-5,911
Dated 8-26-09——
Previously Reported on W-2——

Perforations

Perforated and open-hole intervals.

FromToType
7,4198,069Perforated
8,3888,691Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6252,15811500 S
8.6252,15812.25525 S
5.58,7827.875—
5.5—7.875—

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
00May 24, 2010Nov 30, 2009—
00Mar 1, 2010Aug 28, 2009Yes
00Feb 23, 2010——

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