WELL · 42-033-32858 · DISTRICT 10

Crazy Horse 24-12 #3JH

Permitted

Borden County  · Horizontal

Crazy Horse 24-12 #3JH (API 42-033-32858) 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 July 24, 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 · LATEST PERMIT (NO EWA RECORD)

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitSurge Operating, LLCJul 24, 2026
9,000
total depth, ft
1
permits on file
Jul 24, 2026
last permit issued
—
completed
—
cumulative oil, bbl
—
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS

Surface location

32.679983, -101.414342

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
917366-99DrillSurge Operating, LLCJul 22, 2026Jul 24, 2026—9,000

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 →

Hull 1642-033-32331

5.3 KM · Pie Operating, LLC · Section with this well →

San Andres3,000-2,983
San Andres3,000-2,983
Clear Fork4,300-4,283
Clear Fork5,300-5,283
Strawn8,500-8,483

Mothman Unit a 45-0442-033-32444

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

Santa Rosa2502,110
Rustler2502,110
Yates1,478882
San Andres3,039-679
Clear Fork4,936-2,576
Spraberry5,446-3,086
Wolfcamp6,940-4,580
Wichita-Albany—

10 TOPS · FIRST 8

Benders 41-2942-033-32783

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

Rustler1,0501,311
Yates1,506855
San Andres3,046-685
Glorieta4,597-2,236
Clear Fork4,924-2,563
Spraberry5,429-3,068
Dean6,741-4,380
Wichita-Albany—

10 TOPS · FIRST 8

Lamassu Unit B 44-0542-033-32784

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

Rustler1,0491,311
Yates1,506854
San Andres3,055-695
Glorieta4,609-2,249
Clear Fork4,937-2,577
Spraberry5,444-3,084
Dean6,749-4,389
Wichita-Albany—

10 TOPS · FIRST 8

Unicorn Unit a 04-3742-033-32426

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

Rustler9021,493
Yates2,000395
San Andres3,067-672
Clear Fork4,704-2,309
Spraberry5,340-2,945
Wolfcamp6,670-4,275
Wichita-Albany—
Cisco—

10 TOPS · FIRST 8

Rakshasa Unit B 01-4842-033-32418

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

Rustler9101,484
Yates1,560834
San Andres3,489-1,095
Clear Fork4,944-2,550
Spraberry5,456-3,062
Wolfcamp6,805-4,411
Santa Rosa—
Wichita-Albany—

10 TOPS · FIRST 8

Beaver Valley Ranch 542-033-32299

8.2 KM · Pie Operating, LLC · Section with this well →

Jo Mill6,520-6,503
Mississippian8,874-8,857

Titan Unit 05-0742-033-32563

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

Rustler1,0831,333
San Andres3,021-605
Clear Fork4,913-2,497
Spraberry5,306-2,890
Dean6,628-4,212
Wolfcamp6,662-4,246
Wichita-Albany—
Cisco—

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