WELL · 42-033-00104 · DISTRICT 8

Guilliams Ranch 26 #1R

Plugged

Borden County · Koonsman (Strawn -E-) field  · Vertical

Guilliams Ranch 26 #1R (API 42-033-00104) is a plugged well in Borden County, plugged December 14, 2020, last operated by Shenandoah Petroleum Corporation.

The RRC has issued one drilling permit, issued January 14, 2014, permitted to 8,700 ft.

Completion filings report 10 formation tops, including Cisco, Clear Fork, Leonard, Rustler.

Its lease has reported 4.13K barrels of oil since March 2014, last reporting in November 2021.

Operator of record

Shenandoah Petroleum Corporation

Midland, TX · P-5 Y, filed Aug 4, 2025 · 236 permits on file · (432) 685-1964

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleShenandoah Petroleum Corporation
Production reportsShenandoah Resources LLCthrough Mar 2016
Latest permitShenandoah Petroleum CorporationJan 14, 2014

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

8,700
total depth, ft
1
permits on file
Jan 14, 2014
last permit issued
Mar 1, 2014
completed
4.13K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2014 THROUGH Nov 2021

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 1, 2014
Shut in
—
Plugged
Dec 14, 2020

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Guilliams Ranch 26 O-11-70177Koonsman (Strawn -E-)Shenandoah Petroleum Corporation14.13K0Mar 2014 – Nov 2021

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. 1Shenandoah Petroleum CorporationMar 2014 → Aug 2015
  2. 2Shenandoah Resources LLCSep 2015 → Mar 2016

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
776406-99ReenterShenandoah Petroleum CorporationDec 30, 2013Jan 14, 2014Jan 10, 20148,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-11-70177————

Formation tops

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

FormationMD ftSubsea
CiscoCISCO - ACTIVE CO2 FLOOD——
Clear ForkCLEARFORK——
LeonardLEONARD LIME——
RustlerRUSTLER - GAU PROTECTION——
San AndresSAN ANDRES - HIGH FLOWS, H2S, CO——
Santa RosaSANTA ROSA - GAU PROTECTION——
Spraberry——
Wichita-AlbanyWICHITA ALBANY——
WolfcampWOLFCAMP - STRONG WATER FLOWS——
Yates——

Perforations

Perforated and open-hole intervals.

FromToType
8,2188,226Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6252,79211200 S
5.55,5007.5—
4.58,3087.5150 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
00Aug 22, 2014Apr 30, 2014Yes

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