WELL · 42-353-33759 · DISTRICT 8

Orw MP 113.6 New Soukup #2

N

Nolan County  · Vertical

Orw MP 113.6 New Soukup #2 (API 42-353-33759) is a permitted well in Nolan County filed by Magellan Pipeline Company, L.P.; no completion report is on file yet.

The RRC has issued one drilling permit, issued April 24, 2025, permitted to 550 ft.

Operator of record

Magellan Pipeline Company, L.P.

Tulsa, OK · P-5 Y, filed Apr 4, 2026 · 82 permits on file · (800) 666-9041

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitMagellan Pipeline Company, L.P.Apr 24, 2025
550
total depth, ft
1
permits on file
Apr 24, 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

32.457350, -100.186322

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Nolan 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
907452-99DrillMagellan Pipeline Company, L.P.Apr 15, 2025Apr 24, 2025—550

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.

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 →

Elisa42-353-33398

2.3 KM · Scout Energy Management LLC · Section with this well →

Coleman Junction2,520-473
Coleman Junction2,520-473
Cisco3,170-1,123
Strawn5,119-3,072
Odom5,334-3,287
Cambrian Sand5,492-3,445
Tannehill—
Wolfcamp—

15 TOPS · FIRST 8

Heather42-353-33364

2.7 KM · Scout Energy Management LLC · Section with this well →

Strawn5,074-3,055
Strawn5,078-3,059
Caddo5,438-3,419

Whitaker, E. G.42-353-33231

2.7 KM · Mid-Con Energy Operating, LLC · Section with this well →

Strawn5,132-3,099
T/Ellenburger5,506-3,473

McElmurray 'D'42-353-33411

2.8 KM · Scout Energy Management LLC · Section with this well →

Strawn5,081-3,058
Odom5,284-3,261
Caddo5,429-3,406

W.W. McElmurray 'A'42-353-33433

3.2 KM · Mid-Con Energy Operating, LLC · Section with this well →

Coleman Junction2,468-454
Noodle Creek - Disposal—
Tannehill—
Wichita-Albany—
Wolfcamp—
Flippen Sand - Disposal—
Breckenridge - Disposal—
Elm Creek - Disposal—

10 TOPS · FIRST 8

WW McElmurray 'B'42-353-33597

3.2 KM · Scout Energy Management LLC · Section with this well →

Coleman Junction2,454-1,263
Coleman Junction2,454-1,263
Noodle Creek - Disposal2,777-1,586
B/Noodle Creek Lime2,823-1,632
B/Cisco Lime3,374-2,183
B/Three Finger Shale4,816-3,625
T/Strawn Sand5,013-3,822
T/Strawn Sd.5,013-3,822

20 TOPS · FIRST 8

Tema-Little42-353-33497

3.3 KM · Mid-Con Energy Operating, LLC · Section with this well →

Coleman Junction2,506-495
Elm Creek - Disposal—
Breckenridge - Disposal—
Flippen Lime - Disposal—
Flippen Sand - Disposal—
King Sand - Disposal—
Noodle Creek - Disposal—
Tannehill—

10 TOPS · FIRST 8

Tema-Little42-353-33496

3.3 KM · Mid-Con Energy Operating, LLC · Section with this well →

Coleman Junction2,480-471
Flippen Sand - Disposal—
Wolfcamp—
Flippen Lime - Disposal—
Elm Creek - Disposal—
Wichita-Albany—
Tannehill—
Noodle Creek - Disposal—

10 TOPS · FIRST 8

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