WELL · 42-177-34125 · DISTRICT 1

Arches B #2H

N

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

Arches B #2H (API 42-177-34125) is a horizontal well in Gonzales County operated by Eog Resources Inc., completed September 16, 2019.

The RRC has issued one drilling permit, issued March 13, 2019, permitted to 12,700 ft.

Completion filings report 9 formation tops, including Reklaw, Wilcox, Carrizo, Navarro.

No lease production has been reported under this well’s leases.

Operator of record

EOG Resources Inc.

Based in
Midland, TX
P-5 status
Active (A)
P-5 last filed
Oct 2, 2025
Permits on file
16,348
Phone
(713) 651-7000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEOG Resources Inc.
Production reportsEOG Resources, Inc.through Apr 2026
Latest permitEOG Resources, Inc.Mar 13, 2019
12,700
total depth, ft
1
permits on file
Mar 13, 2019
last permit issued
Sep 16, 2019
completed
0
cumulative oil, bbl
426K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2019 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 16, 2019
Shut in
—
Plugged
—

Surface location

29.281408, -97.446822

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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Arches B G-1-291781Eagleville (Eagle Ford-1)EOG Resources, Inc.10426KSep 2019 – Jul 2026
Arches B O-1-19903Eagleville (Eagle Ford-1)EOG Resources, Inc.100Sep 2019 – Apr 2022

Gas, mcf lease total

Last 12 months 16,965 · prior 12 23,283(-27%)

02K4K202420252026

Chain of custody

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

  1. 1EOG Resources, Inc.Sep 2019 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
850958-99DrillEOG Resources, Inc.Mar 12, 2019Mar 13, 2019Mar 27, 201912,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-1-291781————
—— O-1-19903————

Formation tops

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

FormationMD ftSubsea
Reklaw2,803-2,531
WilcoxWILCOX - DISPOSAL3,324-3,052
Carrizo3,471-3,199
Navarro8,383-8,111
Anacacho10,365-10,093
Austin ChalkAUSTIN CHALK - H2S10,755-10,483
Eagle FordEAGLE FORD - H2S11,198-10,926
BudaBUDA - H2S, DISPOSAL——
EdwardsEDWARDS - H2S——

Perforations

Perforated and open-hole intervals.

FromToType
11,55017,856Perforated
18,89719,979Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,57812.25811 S
620,0378.52,610 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
00Jan 31, 2022Jan 4, 2022Yes
00Jan 13, 2020Oct 31, 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 neighbors, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Arches A42-177-34124

0.0 KM · EOG Resources, Inc. · Section with this well →

Reklaw2,836-2,564
Wilcox3,357-3,085
Carrizo3,504-3,232
Navarro8,416-8,144
Anacacho10,371-10,099
Austin Chalk10,815-10,543
Eagle Ford11,245-10,973
Buda—

9 TOPS · FIRST 8

Arches C42-177-34126

0.0 KM · EOG Resources, Inc. · Section with this well →

Reklaw2,799-2,527
Wilcox3,320-3,048
Carrizo3,467-3,195
Navarro8,379-8,107
Anacacho10,271-9,999
Austin Chalk10,716-10,444
Eagle Ford11,196-10,924
Edwards—

9 TOPS · FIRST 8

Arches D42-177-34127

0.0 KM · EOG Resources, Inc. · Section with this well →

Reklaw2,756-2,484
Wilcox3,277-3,005
Carrizo3,424-3,152
Navarro8,336-8,064
Anacacho10,225-9,953
Austin Chalk10,657-10,385
Eagle Ford11,070-10,798
Edwards—

9 TOPS · FIRST 8

Arches E42-177-34523

0.4 KM · EOG Resources, Inc. · Section with this well →

Reklaw3,003-2,761
Wilcox3,695-3,453
Carrizo3,765-3,523
Navarro8,534-8,292
Anacacho10,141-9,899
Austin Chalk10,478-10,236
Eagle Ford10,988-10,746
Edwards—

9 TOPS · FIRST 8

Arches H42-177-34526

0.4 KM · EOG Resources, Inc. · Section with this well →

Reklaw3,048-2,806
Wilcox3,740-3,498
Carrizo3,841-3,599
Navarro8,544-8,302
Anacacho10,108-9,866
Austin Chalk10,426-10,184
Eagle Ford10,955-10,713
Edwards—

9 TOPS · FIRST 8

Arches G42-177-34525

0.4 KM · EOG Resources, Inc. · Section with this well →

Reklaw3,043-2,801
Wilcox3,735-3,493
Carrizo3,836-3,594
Navarro8,542-8,300
Anacacho10,111-9,869
Austin Chalk10,421-10,179
Eagle Ford10,955-10,713
Edwards—

9 TOPS · FIRST 8

Arches F42-177-34524

0.4 KM · EOG Resources, Inc. · Section with this well →

Reklaw3,044-2,802
Wilcox3,736-3,494
Carrizo3,765-3,523
Navarro8,542-8,300
Anacacho10,131-9,889
Austin Chalk10,428-10,186
Eagle Ford10,952-10,710
Edwards—

9 TOPS · FIRST 8

Pinnacles A42-177-33998

2.6 KM · EOG Resources, Inc. · Section with this well →

Reklaw2,474-2,234
Wilcox3,166-2,926
Carrizo3,267-3,027
Navarro8,022-7,782
Anacacho9,627-9,387
Austin Chalk10,021-9,781
Eagle Ford10,447-10,207
Edwards—

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