TEXAS · WELLS · REEVES COUNTY · API 42-389-33065 · DISTRICT 7B

State Harrison Ranch 56 #1001H

Y

Reeves County · Phantom (Wolfcamp) field · Producing  · Horizontal

State Harrison Ranch 56 #1001H (API 42-389-33065) is a horizontal well in Reeves County operated by Eog Resources Inc., completed February 7, 2013 and listed as producing on the RRC schedule.

The RRC has issued 2 drilling permits (amended 3 times) between 2011 and 2012, permitted to 10,239 ft.

Completion filings report 4 formation tops, including Bone Spring, 2 Nd Bs Sand, 3rd Bs Sand, Wolfcamp.

Its 3 leases have reported 255K barrels of oil and 2.33M mcf of gas since January 2012, last reporting volume in April 2026. The leases carry 13 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,354
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.Sep 10, 2012
10,239
total depth, ft
5
permits on file
Sep 10, 2012
last permit issued
Feb 7, 2013
completed
255K
cumulative oil, bbl
2.33M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2013 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Feb 7, 2013
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active – Extension (X)

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
State Harrison Ranch 56 G-10-283311Phantom (Wolfcamp)EOG Resources, Inc.1255K2.33MFeb 2013 – Apr 2026
Harrison Ranch 56 O-10-42941WildcatEOG Resources, Inc.100Jan 2012 – —
State Harrison Ranch 56 O-10-44356Phantom (Wolfcamp)EOG Resources, Inc.1100Feb 2013 – —

Gas, mcf lease total

Last 12 months 98,413 · prior 12 90,909(+8%)

010K20K202420252026

Chain of custody

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

  1. 1EOG Resources, Inc.Feb 2013 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
746908-97RecompletionEOG Resources, Inc.Feb 25, 2013Sep 10, 2012Dec 4, 201212,290
746908-98RecompletionEOG Resources, Inc.Sep 14, 2012Sep 10, 2012Dec 4, 201212,290
746908-99RecompletionEOG Resources, Inc.Aug 22, 2012Sep 10, 2012—11,600
726715-98DrillEOG Resources, Inc.Jul 29, 2013Oct 26, 2011Dec 4, 201112,290
726715-99DrillEOG Resources, Inc.Oct 20, 2011Oct 26, 2011Dec 4, 201111,600

Completions

CompletedLeaseFieldOperatorStatusDepth
Feb 7, 2013State Harrison Ranch 56 G-10-283311Phantom (Wolfcamp)EOG Resources Inc.Producing10,239
Feb 7, 2013State Harrison Ranch 56 O-10-44356Phantom (Wolfcamp)EOG Resources Inc.Not on Schedule—
Jan 22, 2012Harrison Ranch 56 O-10-42941WildcatEOG Resources Inc.Not on Schedule—

Formation tops

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

FormationMD ftSubsea
Bone Spring2ND BONE SPRING8,330-5,153
2 ND BS Sand8,330-5,153
Bone Spring3RD BONE SPRING9,430-6,253
3RD BS Sand9,430-6,253
Wolfcamp9,828-6,651

Perforations

Perforated and open-hole intervals.

FromToType
10,28014,400Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
261,127202,000 S
201,127262,000 S
17.53,25113.3751,800 S
13.3753,25117.51,800 S
12.2510,3379.6251,850 S
9.62510,33712.251,850 S
8.514,4315.51,325 S
5.514,4318.51,325 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Feb 26, 2018Jan 12, 2018Yes
00Mar 29, 2014Mar 25, 2013—
00Aug 1, 2013Aug 13, 2012Yes

Well logs

1 log loaded from the RRC's log index, the latest received Feb 10, 2015. Density, Neutron, Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYSpans 2 Nd Bs Sand, Bone Spring, 3rd Bs Sand, WolfcampTIFF3,248 to 10,342Feb 10, 2015run Jan 5, 20126.67

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it. The University Lands library has no per-well link: then paste it into its 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/38933065, documented in the API reference.