WELL · 42-033-32820 · DISTRICT 10

Siren Unit 36-48 #3MH

N

Borden County  · Horizontal

Siren Unit 36-48 #3MH (API 42-033-32820) is a permitted horizontal well in Borden County filed by Surge Operating, LLC; no completion report is on file yet.

The RRC has issued one drilling permit, issued December 16, 2025, permitted to 9,000 ft.

Operator of record

Surge Operating, LLC

Houston, TX · P-5 Y, filed May 4, 2026 · 1,234 permits on file · (832) 495-6024

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitSurge Operating, LLCDec 16, 2025
9,000
total depth, ft
1
permits on file
Dec 16, 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.544946, -101.374927

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Borden 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
912189-99DrillSurge Operating, LLCDec 10, 2025Dec 16, 2025Jan 8, 20269,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). 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 →

Siren Unit 36-4842-033-32818

0.0 KM · Surge Operating, LLC · Section with this well →

Rustler1,1721,290
Yates1,717745
San Andres3,181-719
Clear Fork4,986-2,524
Spraberry5,312-2,850
Dean6,585-4,123
Wolfcamp6,670-4,208
Cisco—

10 TOPS · FIRST 8

Sasquatch Unit 36-2442-033-32822

0.0 KM · Surge Operating, LLC · Section with this well →

Rustler1,0281,434
Yates1,500962
San Andres2,916-454
Glorieta4,412-1,950
Clear Fork4,958-2,496
Spraberry5,280-2,818
Dean—
Santa Rosa—

10 TOPS · FIRST 8

Siren Unit 36-4842-033-32817

0.0 KM · Surge Operating, LLC · Section with this well →

Rustler1,1771,285
Yates1,723739
San Andres3,190-728
Clear Fork4,997-2,535
Spraberry5,324-2,862
Dean6,643-4,181
Wolfcamp6,797-4,335
Santa Rosa—

10 TOPS · FIRST 8

Sasquatch Unit 36-2442-033-32543

0.0 KM · Surge Operating, LLC · Section with this well →

Rustler1,0621,401
Yates1,533930
San Andres3,071-608
Clear Fork4,981-2,518
Spraberry6,345-3,882
Dean6,592-4,129
Santa Rosa—
Wolfcamp—

10 TOPS · FIRST 8

Sasquatch Unit 36-2442-033-32539

0.0 KM · Surge Operating, LLC · Section with this well →

Rustler1,0621,401
Yates1,533930
San Andres3,071-608
Clear Fork4,981-2,518
Spraberry6,345-3,882
Dean6,592-4,129
Leonard—
Wichita-Albany—

10 TOPS · FIRST 8

Siren Unit 36-4842-033-32816

0.3 KM · Surge Operating, LLC · Section with this well →

Rustler1,1791,295
Yates1,725749
San Andres3,182-708
Glorieta4,511-2,037
Clear Fork4,976-2,502
Spraberry5,300-2,826
Leonard—
Dean—

10 TOPS · FIRST 8

Siren Unit 36-4842-033-32815

0.3 KM · Surge Operating, LLC · Section with this well →

Rustler1,1931,281
Yates1,737737
San Andres3,196-722
Glorieta4,526-2,052
Clear Fork4,992-2,518
Spraberry5,316-2,842
Dean—
Wichita-Albany—

10 TOPS · FIRST 8

Sasquatch Unit 36-2442-033-32484

0.3 KM · Surge Operating, LLC · Section with this well →

Santa Rosa3252,149
Rustler3252,149
Yates1,578896
San Andres3,209-735
Clear Fork5,016-2,542
Spraberry5,379-2,905
Wolfcamp6,801-4,327
Wichita-Albany—

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