WELL · 42-083-35956 · DISTRICT 7

Adami #8

Y

Coleman County · Coleman County Regular field · Shut IN  · Vertical

Adami #8 (API 42-083-35956) is a well in Coleman County operated by Sands Energy LLC, completed April 25, 2013 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued November 14, 2011, permitted to 4,000 ft.

It was permitted by Window Operating CO., The and has since transferred to Sands Energy LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Morris Sand, Stray Gardner Sand, Gray Sand.

Its lease has reported 13K barrels of oil and 27.2K mcf of gas since April 2013, last reporting in July 2026.

Operator of record

Sands Energy LLC

Permitted by Window Operating Co., The; the EWA schedule now lists a different operator.

Baird, TX · P-5 Y, filed Mar 20, 2026 · (325) 514-4040

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSands Energy LLC
Production reportsWindow Operating Co., Thethrough Sep 2025
Latest permitWindow Operating Co., TheNov 14, 2011

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

4,000
total depth, ft
2
permits on file
Nov 14, 2011
last permit issued
Apr 25, 2013
completed
13K
cumulative oil, bbl
27.2K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2013 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 25, 2013
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
Adami O-8-31218Coleman County RegularSands Energy LLC113K27.2KApr 2013 – Jul 2026

Oil, barrels lease total

Last 12 months 159 · prior 12 435(-63%)

050100202420252026

Chain of custody

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

  1. 1Window Operating Co., TheApr 2013 → Sep 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
727704-98DrillWindow Operating Co., TheMay 14, 2013Nov 14, 2011Dec 7, 20114,000
727704-99DrillWindow Operating Co., TheNov 4, 2011Nov 14, 2011—4,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-31218————

Formation tops

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

FormationMD ftSubsea
Morris Sand2,801-979
Stray Gardner Sand2,937-1,115
Gray Sand3,100-1,278

Perforations

Perforated and open-hole intervals.

FromToType
2,9422,950Perforated
2,9702,976Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62516512.25110 S
4.53,1537.875165 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
00Jun 3, 2013May 30, 2013Yes

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