WELL · 42-177-34370 · DISTRICT 1

Barnhart (EF) C-E SA 1 #1H

Y

Gonzales County · Eagleville (Eagle Ford-1) field · Producing  · Horizontal

Barnhart (EF) C-E SA 1 #1H (API 42-177-34370) is a horizontal well in Gonzales County operated by Marathon Oil EF LLC, completed May 31, 2024 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued February 23, 2021, permitted to 22,000 ft.

Completion filings report 8 formation tops, including Austin Chalk, Reklaw, Carrizo, Wilcox.

Its lease has reported 339K barrels of oil and 622K mcf of gas since March 2021, last reporting in July 2026.

Operator of record

Marathon Oil EF LLC

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Sep 26, 2025
Permits on file
3,191
Phone
(832) 486-2737

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMarathon Oil EF LLC
Production reportsMarathon Oil EF LLCthrough Apr 2026
Latest permitMarathon Oil EF LLCFeb 23, 2021
22,000
total depth, ft
1
permits on file
Feb 23, 2021
last permit issued
May 31, 2024
completed
339K
cumulative oil, bbl
622K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2021 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 31, 2024
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

Surface location

29.247872, -97.493919

Google Maps ↗

Permit surface location from the RRC GIS record, in Gonzales 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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Barnhart (EF) C-E SA 1 O-1-20395Eagleville (Eagle Ford-1)Marathon Oil EF LLC1339K622KMar 2021 – Jul 2026

Oil, barrels lease total

Last 12 months 11,945 · prior 12 23,201(-49%)

02K4K6K202420252026

Gas, mcf lease total

Last 12 months 21,321 · prior 12 44,612(-52%)

02K4K6K202420252026

Chain of custody

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

  1. 1Marathon Oil EF LLCJun 2021 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
867541-99DrillMarathon Oil EF LLCFeb 3, 2021Feb 23, 2021Mar 19, 202122,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-20395————

Formation tops

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

FormationMD ftSubsea
Austin ChalkAUSTIN CHALK - H2S1,365-1,125
Reklaw2,832-2,592
Carrizo3,429-3,189
WilcoxWILCOX - DISPOSAL4,516-4,276
Austin ChalkAUSTIN CHALK - H2S10,365-10,125
Eagle FordEAGLE FORD - H2S10,979-10,739
BudaBUDA - H2S, DISPOSAL——
EdwardsEDWARDS - H2S——
Navarro——

Perforations

Perforated and open-hole intervals.

FromToType
11,43219,804Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6254,93512.251,693 S
5.519,8048.753,716 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 26, 2024Jul 9, 2024Yes
00Feb 22, 2024Feb 2, 2024—
00Jan 18, 2022Dec 30, 2021—
00Jul 29, 2021Jul 9, 2021—
00Apr 27, 2021Apr 6, 2021Yes

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 neighbors, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Barnhart (EF) C-E SA 242-177-34371

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

Reklaw2,832-2,592
Carrizo3,429-3,189
Wilcox4,516-4,276
Austin Chalk10,418-10,178
Eagle Ford10,994-10,754
Buda—
Edwards—
Navarro—

Barnhart (EF) C-E SA 342-177-34372

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

Reklaw2,832-2,594
Carrizo3,429-3,191
Wilcox4,516-4,278
Austin Chalk10,461-10,223
Eagle Ford11,020-10,782
Buda—
Edwards—
Navarro—

Barnhart (EF) 2H Unit SA42-177-34469

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

Reklaw3,319-3,067
Carrizo3,744-3,492
Wilcox3,953-3,701
Austin Chalk11,037-10,785
Eagle Ford11,676-11,424
Navarro—
Edwards—
Buda—

Barnhart (EF) 2H Unit42-177-34470

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

Reklaw3,319-3,067
Carrizo3,744-3,492
Wilcox3,953-3,701
Austin Chalk11,008-10,756
Eagle Ford11,663-11,411
Navarro—
Buda—
Edwards—

Barnhart (EF)42-177-34468

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

Reklaw3,319-3,067
Carrizo3,744-3,492
Wilcox3,953-3,701
Austin Chalk10,999-10,747
Eagle Ford11,626-11,374
Edwards—
Navarro—
Buda—

Barnhart (EF) 2H Unit42-177-34471

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

Reklaw3,319-3,067
Carrizo3,744-3,492
Wilcox3,853-3,601
Austin Chalk10,999-10,747
Eagle Ford11,662-11,410
Navarro—
Buda—
Edwards—

Barnhart (EF)42-177-34467

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

Reklaw3,319-3,072
Carrizo3,744-3,497
Wilcox3,953-3,706
Austin Chalk10,990-10,743
Eagle Ford11,598-11,351
Buda—
Navarro—
Edwards—

Barnhart (EF) 2H Unit-J Unit SA42-177-34472

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

Reklaw3,319-3,071
Carrizo3,744-3,496
Wilcox3,953-3,705
Austin Chalk11,001-10,753
Eagle Ford11,667-11,419
Edwards—
Navarro—
Buda—

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