WELL · 42-295-33317 · DISTRICT 10

Cooper 435 #2H

Plugged

Lipscomb County · Lipscomb (Cleveland) field  · Horizontal

Cooper 435 #2H (API 42-295-33317) is a plugged horizontal well in Lipscomb County, plugged January 12, 2021, last operated by Highmark Energy Operating LLC.

The RRC has issued one drilling permit, issued April 4, 2008, permitted to 9,000 ft.

It was permitted by Eog Resources, Inc. and has since transferred to Highmark Energy Operating LLC on the wellbore schedule.

Completion filings report 2 formation tops, including Checkerboard Limestone, Cleveland.

Its lease has reported 196K barrels of oil and 2.15M mcf of gas since July 2008, last reporting in July 2023. The lease carries 4 wells, so these are lease totals, not this well alone.

Operator of record

Highmark Energy Operating LLC

Permitted by EOG Resources, Inc.; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Mar 9, 2026
Permits on file
23
Phone
(469) 214-5299

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHighmark Energy Operating LLC
Production reportsEOG Resources, Inc.through Apr 2020
Latest permitEOG Resources, Inc.Apr 4, 2008

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

9,000
total depth, ft
1
permits on file
Apr 4, 2008
last permit issued
Jan 7, 2009
completed
196K
cumulative oil, bbl
2.15M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2008 THROUGH Jul 2023

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 7, 2009
Shut in
—
Plugged
Jan 12, 2021

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Cooper 435 O-14-7883Lipscomb (Cleveland)Highmark Energy Operating, LLC4196K2.15MJul 2008 – Jul 2023

No volumes reported on these leases in the last three years.

Chain of custody

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

  1. 1EOG Resources, Inc.Jul 2008 → Apr 2020

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
657892-99DrillEOG Resources, Inc.Mar 20, 2008Apr 4, 2008Aug 14, 20089,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-14-7883————

Formation tops

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

FormationMD ftSubsea
Checkerboard Limestone8,140-5,610
Cleveland8,254-5,724

Perforations

Perforated and open-hole intervals.

FromToType
8,68012,375Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,79012.25760 S
4.512,4468.751,245 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
00Apr 29, 2009Feb 3, 2009Yes
00Apr 8, 2009——

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