WELL · 42-177-34848 · DISTRICT 1

Barnhart (EF) #207H

Permitted

Gonzales County  · Horizontal

Barnhart (EF) #207H (API 42-177-34848) is a permitted horizontal well in Gonzales County filed by Ensign Natural Resources II LLC; no completion report is on file yet.

The RRC has issued one drilling permit (amended once), issued July 16, 2026, permitted to 17,500 ft.

Operator of record

Ensign Natural Resources II LLC

Houston, TX · P-5 Y · 13 permits on file · (830) 407-2622

SOURCE · LATEST PERMIT (NO EWA RECORD)

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitMarathon Oil EF LLCJul 16, 2026
17,500
total depth, ft
2
permits on file
Jul 16, 2026
last permit issued
—
completed
—
cumulative oil, bbl
—
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS

Surface location

29.316772, -97.491169

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Gonzales 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
917219-98DrillEnsign Natural Resources II LLCAug 31, 2026Jul 16, 2026Jul 30, 202617,500
917219-99DrillMarathon Oil EF LLCJul 14, 2026Jul 16, 2026—17,500

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 →

Barnhart (EF)42-177-32494

0.2 KM · Marathon Oil EF LLC · Section with this well →

Anacacho8,760-8,504
Austin Chalk8,903-8,647
Eagle Ford9,340-9,084
Eagle Ford9,340-9,084

Barnhart (Ef)-HFS SA842-177-34755

1.0 KM · Marathon Oil EF LLC · Section with this well →

Reklaw2,375-2,097
Carrizo2,516-2,238
Wilcox2,824-2,546
Austin Chalk8,840-8,562
Eagle Ford9,269-8,991
Edwards—
Buda—
Navarro—

Barnhart (Ef)-HFS SA742-177-34754

1.0 KM · Marathon Oil EF LLC · Section with this well →

Reklaw2,372-2,135
Carrizo2,513-2,276
Wilcox2,820-2,583
Austin Chalk8,841-8,604
Austin Chalk8,841-8,604
Eagle Ford9,279-9,042
Eagle Ford9,279-9,042
Edwards—

10 TOPS · FIRST 8

Barnhart (Ef)-HFS SA642-177-34753

1.0 KM · Marathon Oil EF LLC · Section with this well →

Reklaw2,368-2,131
Carrizo2,509-2,272
Wilcox2,814-2,577
Austin Chalk8,702-8,465
Eagle Ford9,134-8,897
Edwards—
Navarro—
Buda—

Barnhart (Ef)-HFS SA542-177-34752

1.0 KM · Marathon Oil EF LLC · Section with this well →

Reklaw2,367-2,130
Carrizo2,507-2,270
Wilcox2,811-2,574
Austin Chalk8,667-8,430
Eagle Ford9,100-8,863
Edwards—
Navarro—
Buda—

Barnhart (Ef)-HFS SA442-177-34751

1.0 KM · Marathon Oil EF LLC · Section with this well →

Reklaw2,366-2,129
Carrizo2,505-2,268
Wilcox2,810-2,573
Austin Chalk8,682-8,445
Eagle Ford9,110-8,873
Edwards—
Navarro—
Buda—

Barnhart (Ef)-HFS SA342-177-34750

1.0 KM · Marathon Oil EF LLC · Section with this well →

Reklaw2,068373
Carrizo2,628-187
Wilcox2,863-422
Austin Chalk8,808-6,367
Eagle Ford9,253-6,812
Navarro—
Edwards—
Buda—

Barnhart (Ef)-HFS SA242-177-34749

1.0 KM · Marathon Oil EF LLC · Section with this well →

Reklaw2,068-1,827
Carrizo2,628-2,387
Wilcox2,863-2,622
Austin Chalk8,799-8,558
Eagle Ford9,248-9,007
Edwards—
Buda—
Navarro—

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