WELL · 42-033-32831 · DISTRICT 10

Wendigo Unit B 10-14 #5MH

N

Borden County  · Horizontal

Wendigo Unit B 10-14 #5MH (API 42-033-32831) 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 February 3, 2026, 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, LLCFeb 3, 2026
9,000
total depth, ft
1
permits on file
Feb 3, 2026
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.562303, -101.328499

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
913210-99DrillSurge Operating, LLCFeb 2, 2026Feb 3, 2026—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). 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 →

Yeti Unit B 10-0642-033-32562

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

Rustler1,0271,379
Yates1,448958
San Andres2,908-502
Clear Fork4,503-2,097
Spraberry6,024-3,618
Dean6,311-3,905
Wolfcamp6,490-4,084
Leonard—

10 TOPS · FIRST 8

Wendigo Unit B 10-1442-033-32560

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

Rustler1,0801,325
Yates1,468937
San Andres2,974-569
Clear Fork4,533-2,128
Spraberry5,032-2,627
Dean6,295-3,890
Wolfcamp6,397-3,992
Wichita-Albany—

10 TOPS · FIRST 8

Yeti Unit B 10-0642-033-32561

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

Rustler1,2091,197
Yates1,507899
San Andres2,913-507
Clear Fork4,531-2,125
Spraberry5,075-2,669
Dean6,239-3,833
Wolfcamp6,332-3,926
Wichita-Albany—

10 TOPS · FIRST 8

Wendigo Unit B 10-1442-033-32559

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

Rustler1,2051,201
Yates1,509897
San Andres2,931-525
Clear Fork4,569-2,163
Spraberry5,120-2,714
Dean6,355-3,949
Wolfcamp6,483-4,077
Leonard—

10 TOPS · FIRST 8

Wendigo Unit B 10-1442-033-32653

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

San Andres2,993-580
Clear Fork4,591-2,178
Spraberry5,121-2,708
Dean6,287-3,874
Wolfcamp6,386-3,973
Cisco—
Carmack—
Canyon—

10 TOPS · FIRST 8

Wendigo Unit a 10-1542-033-32652

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

Rustler1,1331,280
Yates1,535878
San Andres3,039-626
Clear Fork4,647-2,234
Spraberry5,181-2,768
Dean6,354-3,941
Wolfcamp6,446-4,033
Santa Rosa—

10 TOPS · FIRST 8

Yeti Unit B 10-0642-033-32582

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

Yates1,547859
San Andres2,935-529
Clear Fork4,528-2,122
Dean5,061-2,655
Spraberry5,136-2,730
Wolfcamp6,348-3,942
Leonard—
Rustler—

10 TOPS · FIRST 8

Yeti Unit a 10-0642-033-32581

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

Rustler1,2631,152
Yates1,567848
San Andres2,989-574
Clear Fork4,627-2,212
Spraberry5,178-2,763
Dean6,413-3,998
Wolfcamp6,541-4,126
Leonard—

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