WELL · 42-255-33974 · DISTRICT 2

Marek Unit #10H

Y

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

Marek Unit #10H (API 42-255-33974) is a horizontal well in Karnes County operated by Eog Resources Inc., completed January 21, 2015 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued July 19, 2014, permitted to 12,000 ft.

Completion filings report 10 formation tops, including Queen City, Reklaw, Wilcox, Carrizo.

Its lease has reported 3.84M barrels of oil and 5.04M mcf of gas since December 2011, last reporting in July 2026. The lease carries 11 wells, so these are lease totals, not this well alone.

Operator of record

EOG Resources Inc.

Midland, TX · P-5 Y, filed Jul 4, 2026 · 16,348 permits on file · (713) 594-5431

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.Jul 19, 2014
12,000
total depth, ft
1
permits on file
Jul 19, 2014
last permit issued
Jan 21, 2015
completed
3.84M
cumulative oil, bbl
5.04M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 2011 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 21, 2015
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Marek Unit O-2-9878Eagleville (Eagle Ford-2)EOG Resources, Inc.113.84M5.04MDec 2011 – Jul 2026

Oil, barrels lease total

Last 12 months 67,646 · prior 12 72,429(-7%)

05K10K202420252026

Gas, mcf lease total

Last 12 months 139,120 · prior 12 125,065(+11%)

010K20K202420252026

Chain of custody

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

  1. 1EOG Resources, Inc.Dec 2011 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
789573-99DrillEOG Resources, Inc.Jun 16, 2014Jul 19, 2014Nov 21, 201412,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-2-9878————

Formation tops

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

FormationMD ftSubsea
Queen City3,094-2,719
Reklaw3,606-3,231
WilcoxWILCOX - DISPOSAL4,035-3,660
Carrizo4,208-3,833
Anacacho10,600-10,225
Austin ChalkAUSTIN CHALK - H2S10,789-10,414
Eagle FordEAGLE FORD - H2S11,037-10,662
EdwardsEDWARDS - H2S——
FrioFRIO - DISPOSAL——
YeguaYEGUA - DISPOSAL——

Perforations

Perforated and open-hole intervals.

FromToType
11,31017,349Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,50412.25735 S
5.517,4458.52,470 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
00Oct 2, 2015Feb 23, 2015Yes

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