TEXAS · WELLS · LOVING COUNTY · API 42-301-32274 · DISTRICT 7B

State Galileo #2H

Plugged

Loving County · Sandbar (Bone Spring) field  · Horizontal

State Galileo #2H (API 42-301-32274) is a plugged horizontal well in Loving County, plugged November 6, 2025, last operated by Eog Resources Inc..

The RRC has issued one drilling permit (amended once), issued August 9, 2014, permitted to 11,000 ft.

Completion filings report 10 formation tops, including Bell Canyon, Cherry Canyon, Brushy Canyon, Bone Spring.

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 Jan 2022
Latest permitEOG Resources, Inc.Aug 9, 2014
11,000
total depth, ft
2
permits on file
Aug 9, 2014
last permit issued
Feb 12, 2015
completed
0
cumulative oil, bbl
1.69M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2015 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 12, 2015
Shut in
—
Plugged
Nov 6, 2025

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
State Galileo G-10-283907Sandbar (Bone Spring)EOG Resources, Inc.101.69MFeb 2015 – Jul 2026
State Galileo O-10-46107Sandbar (Bone Spring)EOG Resources, Inc.700Jan 2015 – Feb 2019

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.Feb 2015 → Jan 2022

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
790860-98DrillEOG Resources, Inc.Oct 7, 2014Aug 9, 2014Nov 24, 201411,000
790860-99DrillEOG Resources, Inc.Jul 2, 2014Aug 9, 2014Nov 24, 201411,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Feb 12, 2015State Galileo G-10-283907Sandbar (Bone Spring)EOG Resources Inc.Plugged—
Feb 12, 2015State Galileo O-10-46107Sandbar (Bone Spring)EOG Resources Inc.Plugged—

Formation tops

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

FormationMD ftSubsea
Bell Canyon4,642-1,571
Cherry Canyon5,690-2,619
Brushy Canyon7,185-4,114
Bone SpringBONE SPRINGS8,803-5,732
AtokaATOKA - HIGH PRESSURE——
Delaware——
Pennsylvanian——
Red Bluff——
Strawn——
Wolfcamp——

Perforations

Perforated and open-hole intervals.

FromToType
9,33114,146Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62592612.25400 S
5.514,2708.752,000 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
00May 15, 2018Feb 27, 2018—
00May 14, 2015Mar 5, 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) and the University Lands library. 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/30132274, documented in the API reference.