WELL · 42-103-37604 · DISTRICT 10

Waterlogged #22SD

N

Crane County  · Vertical

Waterlogged #22SD (API 42-103-37604) is a permitted well in Crane County filed by Nile Midstream, LLC; no completion report is on file yet.

The RRC has issued one drilling permit (amended once), issued March 26, 2025, permitted to 9,000 ft.

Operator of record

Nile Midstream, LLC

Fort Worth, TX · P-5 Y, filed Sep 4, 2025 · 7 permits on file · (432) 242-0050

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitBlackbeard Operating, LLCMar 26, 2025
9,000
total depth, ft
2
permits on file
Mar 26, 2025
last permit issued
—
completed
—
cumulative oil, bbl
—
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

Surface location

31.489525, -102.696168

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Crane County.

Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
906912-98DrillNile Midstream, LLCJul 30, 2025Mar 26, 2025—9,000
906912-99DrillBlackbeard Operating, LLCMar 25, 2025Mar 26, 2025—9,000

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) and the University Lands library. then paste it into their search.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well has no tops filed, so it cannot anchor a section; its neighbours can.

Section of the neighbours →

Waddell, W. N. Etal42-103-01941

0.3 KM · Burlington Res O & G Co-Midland · Section with this well →

Yates1,577991
McElroy2,421147
Grayburg2,55810
San Andres2,766-198
Judkins2,769-201
McKnight3,273-705
Tubb4,365-1,797

Waddell TR A42-103-01916

0.5 KM · Blackbeard Operating, LLC · Section with this well →

Rustler3732,219
McElroy2,433159
Grayburg2,57022
San Andres2,782-190
San Angelo3,614-1,022
Clear Fork3,990-1,398
Tubb4,354-1,762

Waddell, W. N. et AL42-103-01838

0.5 KM · Burlington Res O & G Co-Midland · Section with this well →

Red Bed4552,108
Anhy, Salt & Gypsum1,4061,157
Anhy & Lime2,365198
Judkins2,755-192
Tubb4,363-1,800
Waddell5,956-3,393

W.N. Waddell Etal42-103-02078

0.6 KM · Burlington Res O & G Co-Midland · Section with this well →

Rustler3832,198
Yates1,593988
Seven Rivers1,830751
Queen2,345236
McElroy2,467114
Grayburg2,611-30
Judkins2,823-242
McKnight3,360-779

15 TOPS · FIRST 8

Waddell TR A42-103-37157

0.8 KM · Blackbeard Operating, LLC · Section with this well →

Rustler3682,220
Yates1,608980
Seven Rivers1,826762
Queen2,348240
Grayburg2,605-17
San Andres2,832-244
McKnight3,332-744
Tubb4,427-1,839

13 TOPS · FIRST 8

Waddell TR A42-103-01701

0.8 KM · Blackbeard Operating, LLC · Section with this well →

Rustler3712,222
Yates1,596997
Seven Rivers1,837756
Queen2,353240
Grayburg2,609-16
San Andres2,818-225
San Angelo3,653-1,060
Clear Fork4,041-1,448

12 TOPS · FIRST 8

Waddell, W. N. et AL42-103-01813

0.8 KM · Burlington Res O & G Co-Midland · Section with this well →

Rustler3482,210
Yates1,5211,037
Seven Rivers1,753805
Queen2,259299
McElroy2,379179
Grayburg2,51543
Judkins2,715-157
McKnight3,222-664

12 TOPS · FIRST 8

Waddell, W. N. et AL42-103-01990

1.1 KM · Gulf Oil Corp. · Section with this well →

Judkins3,021-420
McKnight3,314-713
Tubb4,425-1,824

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