WELL · 42-255-34974 · DISTRICT 2

Hickok #2H

Y

Karnes County · Eagleville (Eagle Ford-2) field · Shut IN  · Horizontal

Hickok #2H (API 42-255-34974) is a horizontal well in Karnes County operated by Eog Resources Inc., completed July 18, 2016 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit, issued March 21, 2016, permitted to 11,500 ft.

Completion filings report 10 formation tops, including Frio, Yegua, Queen City, Reklaw.

Its lease has reported 2.91M barrels of oil and 5.61M mcf of gas since August 2014, last reporting in July 2026. The lease carries 8 wells, so these are lease totals, not this well alone.

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 21, 2016
11,500
total depth, ft
1
permits on file
Mar 21, 2016
last permit issued
Jul 18, 2016
completed
2.91M
cumulative oil, bbl
5.61M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2014 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 18, 2016
Shut in
—
Plugged
—

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

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

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 8 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Hickok O-2-10918Eagleville (Eagle Ford-2)EOG Resources, Inc.82.91M5.61MAug 2014 – Jul 2026

Oil, barrels lease total

Last 12 months 53,918 · prior 12 77,350(-30%)

05K10K202420252026

Gas, mcf lease total

Last 12 months 146,081 · prior 12 146,154(0%)

010K20K30K202420252026

Chain of custody

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

  1. 1EOG Resources, Inc.Aug 2014 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
814330-99DrillEOG Resources, Inc.Mar 10, 2016Mar 21, 2016Apr 8, 201611,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-2-10918————

Formation tops

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

FormationMD ftSubsea
FrioFRIO - DISPOSAL600-221
YeguaYEGUA - DISPOSAL1,500-1,121
Queen City3,120-2,741
Reklaw3,495-3,116
WilcoxWILCOX - DISPOSAL4,203-3,824
Anacacho8,735-8,356
Austin ChalkAUSTIN CHALK - H2S9,270-8,891
Eagle FordEAGLE FORD - H2S9,357-8,978
Carrizo——
EdwardsEDWARDS - H2S——

Perforations

Perforated and open-hole intervals.

FromToType
11,35516,393Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,61312.25660 S
5.516,4868.52,130 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
00Aug 23, 2016Aug 8, 2016Yes

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.

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