WELL · 42-479-44610 · DISTRICT 1

Galvan Ranch #B906H

Y

Webb County · Lorenzo (Austin Chalk) field · Producing  · Horizontal

Galvan Ranch #B906H (API 42-479-44610) is a horizontal well in Webb County operated by SM Energy Company, completed January 17, 2023 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued February 24, 2022, permitted to 8,900 ft.

Completion filings report 12 formation tops, including Wilcox, Midway, Escondido, Olmos.

No lease production has been reported under this well’s leases.

Operator of record

SM Energy Company

Midland, TX · P-5 Y, filed Jul 4, 2026 · 2,485 permits on file · (432) 563-8316

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSM Energy Company
Production reportsSM Energy Companythrough Apr 2026
Latest permitSM Energy CompanyFeb 24, 2022
8,900
total depth, ft
1
permits on file
Feb 24, 2022
last permit issued
Jan 17, 2023
completed
0
cumulative oil, bbl
2.66M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2022 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 17, 2023
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

28.037522, -99.693111

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Webb County.

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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Galvan Ranch G-1-293223Lorenzo (Austin Chalk)SM Energy Company102.66MApr 2022 – Jul 2026

Gas, mcf lease total

Last 12 months 315,942 · prior 12 455,514(-31%)

050K100K150K202420252026

Chain of custody

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

  1. 1SM Energy CompanyOct 2022 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
877281-99DrillSM Energy CompanyFeb 21, 2022Feb 24, 2022Jul 15, 20228,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-1-293223————

Formation tops

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

FormationMD ftSubsea
WilcoxWILCOX - INJECTION/DISPOSAL2,345-1,692
Midway3,501-2,848
EscondidoESCONDITO - INJECTION/DISPOSAL;4,110-3,457
OlmosOLMOS - INJECTION/DISPOSAL5,513-4,860
San Miguel7,270-6,617
Anacacho7,997-7,344
CatahoulaCATAHOULA-FRIO - INJECTION/DISPO——
Cook Mountain——
Eagle FordEAGLE FORD SHALE——
JacksonJACKSON - INJECTION/DISPOSAL——
Queen CityQUEEN CITY - INJECTION/DISPOSAL;——
YeguaYEGUA - INJECTION/DISPOSAL——

Perforations

Perforated and open-hole intervals.

FromToType
9,08121,185Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6253,82612.25855 S
5.521,1698.753,055 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
00Feb 17, 2023Jan 23, 2023Yes
00Feb 9, 2023Jan 13, 2023—
00Oct 5, 2022Sep 1, 2022Yes

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.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Galvan Ranch42-479-44611

0.0 KM · SM Energy Company · Section with this well →

Wilcox2,345-1,692
Escondido4,109-3,456
Olmos5,618-4,965
Anacacho8,031-7,378
Catahoula—
Jackson—
Queen City—
Yegua—

11 TOPS · FIRST 8

Galvan Ranch42-479-44282

0.9 KM · SM Energy Company · Section with this well →

Wilcox2,394-1,746
Midway3,614-2,966
Escondido4,103-3,455
Olmos5,530-4,882
San Miguel7,103-6,455
Anacacho7,996-7,348
Austin Chalk8,503-7,855
Yegua—

12 TOPS · FIRST 8

Galvan Ranch42-479-44283

0.9 KM · SM Energy Company · Section with this well →

Wilcox2,394-1,746
Escondido4,103-3,455
Olmos5,530-4,882
San Miguel7,103-6,455
Anacacho7,996-7,348
Austin Chalk8,503-7,855
Eagle Ford—
Edwards—

14 TOPS · FIRST 8

Galvan Ranch42-479-44186

1.0 KM · SM Energy Company · Section with this well →

Escondido4,185-3,524
Olmos5,614-4,953
San Miguel7,176-6,515
Anacacho8,046-7,385
Austin Chalk8,543-7,882
Yegua—
Wilcox—
Edwards—

13 TOPS · FIRST 8

Galvan Ranch42-479-44854

1.6 KM · SM Energy Company · Section with this well →

Escondido4,142-3,473
Olmos5,704-5,035
San Miguel7,180-6,511
Anacacho8,025-7,356
Austin Chalk8,572-7,903
Yegua—
Catahoula—
Cook Mountain—

13 TOPS · FIRST 8

Galvan Ranch42-479-44853

1.6 KM · SM Energy Company · Section with this well →

Wilcox2,490-1,821
Escondido4,148-3,479
Olmos5,708-5,039
Anacacho8,038-7,369
Eagle Ford—
Yegua—
Queen City—
Jackson—

11 TOPS · FIRST 8

Galvan Ranch42-479-44852

1.6 KM · SM Energy Company · Section with this well →

Wilcox2,494-1,825
Midway3,685-3,016
Escondido4,119-3,450
Olmos5,719-5,050
San Miguel7,197-6,528
Anacacho8,066-7,397
Austin Chalk8,633-7,964
Queen City—

14 TOPS · FIRST 8

Galvan Ranch42-479-44284

1.8 KM · SM Energy Company · Section with this well →

Wilcox2,352-1,706
Midway3,601-2,955
Escondido4,074-3,428
Olmos5,555-4,909
San Miguel7,100-6,454
Anacacho7,965-7,319
Austin Chalk8,476-7,830
Catahoula—

12 TOPS · FIRST 8

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