WELL · 42-033-32465 · DISTRICT 8

Nessie Unit a 34-46 #2AH

Y

Borden County · Spraberry (Trend Area) field · Producing  · Horizontal

Nessie Unit A 34-46 #2AH (API 42-033-32465) is a horizontal well in Borden County operated by Surge Operating LLC, completed September 23, 2018 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued April 20, 2018, permitted to 10,000 ft.

Completion filings report 10 formation tops, including Rustler, Santa Rosa, Yates, San Andres.

Its lease has reported 1.59M barrels of oil and 2.5M mcf of gas since February 2018, last reporting in July 2026. The lease carries 4 wells, so these are lease totals, not this well alone.

Operator of record

Surge Operating LLC

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

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSurge Operating LLC
Production reportsSurge Operating, LLCthrough Mar 2026
Latest permitSurge Operating, LLCApr 20, 2018
10,000
total depth, ft
2
permits on file
Apr 20, 2018
last permit issued
Sep 23, 2018
completed
1.59M
cumulative oil, bbl
2.5M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2018 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Sep 23, 2018
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

32.537044, -101.411658

OpenStreetMap → ·  Google Maps →

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

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; they carry 4 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Nessie Unit a 34-46 O-10-50230Spraberry (Trend Area)Surge Operating, LLC41.59M2.5MFeb 2018 – Jul 2026

Oil, barrels lease total

Last 12 months 80,381 · prior 12 106,525(-25%)

05K10K15K202420252026

Gas, mcf lease total

Last 12 months 316,827 · prior 12 354,351(-11%)

020K40K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Surge Operating, LLCFeb 2018 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
838988-98DrillSurge Operating, LLCMay 11, 2018Apr 20, 2018May 7, 201810,000
838988-99DrillSurge Operating, LLCApr 17, 2018Apr 20, 2018May 7, 201810,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-50230————

Formation tops

As filed on W-2/G-1. Subsea from 2,480 ft elevation.Download CSV →

FormationMD ftSubsea
RustlerRUSTLER - GAU PROTECTION2002,280
Santa RosaSANTA ROSA - GAU PROTECTION2002,280
Yates1,680800
San AndresSAN ANDRES - HIGH FLOWS, H2S, CO3,190-710
Clear ForkCLEARFORK5,010-2,530
Spraberry5,322-2,842
WolfcampWOLFCAMP - STRONG WATER FLOWS6,975-4,495
CiscoCISCO - ACTIVE CO2 FLOOD——
LeonardLEONARD LIME——
Wichita-AlbanyWICHITA ALBANY——

Perforations

Perforated and open-hole intervals.

FromToType
7,53019,741Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37549817.5540 S
9.6257,01312.25540 S
5.519,8798.53,048 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Jun 13, 2019Feb 22, 2019Yes

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's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Orthrus Unit a 34-2242-033-32471

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

Santa Rosa2002,280
Rustler2002,280
Yates1,687793
San Andres3,324-844
Clear Fork5,231-2,751
Spraberry5,592-3,112
Wolfcamp7,008-4,528
Cisco—

10 TOPS · FIRST 8

Nessie Unit a 34-4642-033-32461

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

Rustler2002,278
Santa Rosa2002,278
Yates1,684794
San Andres3,300-822
Clear Fork5,194-2,716
Spraberry5,506-3,028
Wolfcamp6,988-4,510
Leonard—

10 TOPS · FIRST 8

Orthus Unit a 34-2242-033-32466

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

Santa Rosa2002,280
Rustler2002,280
Yates1,687793
San Andres3,318-838
Spraberry5,587-3,107
Wolfcamp6,996-4,516
Clear Fork52,327-49,847
Cisco—

10 TOPS · FIRST 8

Gunsight42-033-32446

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

Rustler1,2011,286
Yates1,701786
San Andres3,322-835
Clear Fork5,337-2,850
Spraberry5,591-3,104
Wolfcamp7,023-4,536
Santa Rosa—
Leonard—

10 TOPS · FIRST 8

Medusa Unit B 28-2142-033-32493

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

Santa Rosa4502,018
Rustler4502,018
Yates1,665803
San Andres3,297-829
Clear Fork5,217-2,749
Spraberry5,602-3,134
Wolfcamp7,009-4,541
Cisco—

10 TOPS · FIRST 8

Medusa Unit B 28-2142-033-32492

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

Santa Rosa4502,019
Rustler4502,019
Yates1,657812
San Andres3,324-855
Clear Fork5,235-2,766
Spraberry5,579-3,110
Wolfcamp6,997-4,528
Wichita-Albany—

10 TOPS · FIRST 8

Medusa Unit C 28-0942-033-32523

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

Rustler4502,028
Santa Rosa4502,028
Yates1,712766
San Andres3,306-828
Clear Fork4,104-1,626
Spraberry5,560-3,082
Wolfcamp6,854-4,376
Cisco—

10 TOPS · FIRST 8

Orthrus Unit B 34-2242-033-32500

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

Santa Rosa2002,314
Rustler2002,314
Yates1,701813
San Andres3,322-808
Clear Fork5,164-2,650
Spraberry5,547-3,033
Wolfcamp6,948-4,434
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/03332465, documented in the API reference.