WELL · 42-163-34037 · DISTRICT 1

Hausser #J 2H

N

Frio County  · Horizontal

Hausser #J 2H (API 42-163-34037) is a permitted horizontal well in Frio County filed by SN Operating, LLC; no completion report is on file yet.

The RRC has issued 2 drilling permits between 2016 and 2021, permitted to 9,000 ft.

Completion filings report 10 formation tops, including Midway, Escondido, Olmos, San Miguel.

Its lease has reported 6.83M barrels of oil and 2.48M mcf of gas since July 2013, last reporting in July 2026. The lease carries 39 wells, so these are lease totals, not this well alone.

Operator of record

SN Operating, LLC

Houston, TX · P-5 Y, filed Jan 14, 2023 · 581 permits on file · (855) 219-1661

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsFormentera Operations LLCthrough Apr 2026
Latest permitSN Operating, LLCApr 9, 2021
9,000
total depth, ft
2
permits on file
Apr 9, 2021
last permit issued
—
completed
6.83M
cumulative oil, bbl
2.48M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2013 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

Surface location

28.826861, -99.358528

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Frio 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 39 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Hausser O-1-17183Briscoe Ranch (Eagleford)Formentera Operations LLC396.83M2.48MJul 2013 – Jul 2026

Oil, barrels lease total

Last 12 months 241,123 · prior 12 271,077(-11%)

010K20K30K202420252026

Gas, mcf lease total

Last 12 months 175,060 · prior 12 187,205(-6%)

010K20K202420252026

Chain of custody

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

  1. 1Sanchez Oil & Gas CorporationJul 2013 → Apr 2014
  2. 2SN Operating, LLCMay 2014 → Jan 2022
  3. 3Formentera Operations LLCFeb 2022 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
868921-99RecompletionSN Operating, LLCApr 6, 2021Apr 9, 2021—9,000
820833-99DrillSN Operating, LLCNov 30, 2016Dec 15, 2016Mar 29, 20179,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-17183————

Formation tops

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

FormationMD ftSubsea
Midway3,111-2,537
Escondido3,492-2,918
Olmos4,404-3,830
San Miguel4,994-4,420
Anacacho5,547-4,973
Austin ChalkAUSTIN CHALK - H2S5,999-5,425
Eagle FordEAGLE FORD - H2S6,619-6,045
BudaBUDA - H2S——
Navarro——
Queen City——

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6253,28312.25655 S
5.512,0218.751,710 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
00Jul 3, 2018May 14, 2018Yes

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 →

Hausser42-163-34041

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

Midway3,105-2,531
Escondido3,524-2,950
Olmos4,401-3,827
San Miguel4,982-4,408
Anacacho5,546-4,972
Austin Chalk6,000-5,426
Eagle Ford6,525-5,951
Navarro—

10 TOPS · FIRST 8

Calvert Ranch Fro42-163-34098

1.5 KM · Exco Operating Company, LP · Section with this well →

Escondido3,622-3,032
Olmos4,616-4,026
Anacacho5,747-5,157
Austin Chalk6,035-5,445
Eagle Ford6,566-5,976
Pearsall—
Queen City—
Buda—

10 TOPS · FIRST 8

Guy Bob Fro42-163-34110

2.4 KM · Exco Operating Company, LP · Section with this well →

Escondido3,606-3,050
Olmos4,573-4,017
Anacacho5,672-5,116
Austin Chalk5,998-5,442
Eagle Ford6,475-5,919
Pearsall—
Queen City—
Georgetown—

10 TOPS · FIRST 8

Harlan RK42-163-34341

2.4 KM · Trailblazer Energy Resources,llc · Section with this well →

Escondido3,400-2,811
Olmos4,440-3,851
Anacacho5,447-4,858
Austin Chalk5,883-5,294
Eagle Ford6,355-5,766
Pearsall—
Buda—
Georgetown—

10 TOPS · FIRST 8

Harlan RK42-163-34340

2.4 KM · Trailblazer Energy Resources,llc · Section with this well →

Escondido3,399-2,810
Olmos4,409-3,820
Anacacho5,460-4,871
Austin Chalk5,900-5,311
Eagle Ford6,364-5,775
Queen City—
Buda—
Georgetown—

10 TOPS · FIRST 8

Guy Bob Fro42-163-34095

2.7 KM · Exco Operating Company, LP · Section with this well →

Escondido3,590-3,032
Olmos4,588-4,030
Anacacho5,643-5,085
Austin Chalk5,973-5,415
Eagle Ford6,441-5,883
Pearsall—
Queen City—
Georgetown—

10 TOPS · FIRST 8

Guy Bob Fro42-163-34111

2.7 KM · Exco Operating Company, LP · Section with this well →

Escondido3,549-2,990
Olmos4,516-3,957
Anacacho5,615-5,056
Austin Chalk5,945-5,386
Eagle Ford6,407-5,848
Navarro—
Pearsall—
Georgetown—

10 TOPS · FIRST 8

Valyn Clara42-163-34007

3.1 KM · SN Operating, LLC · Section with this well →

Escondido3,510-2,937
Olmos4,382-3,809
Anacacho5,447-4,874
Austin Chalk5,895-5,322
Eagle Ford6,397-5,824
Buda—
Georgetown—
Pearsall—

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