WELL · 42-415-34755 · DISTRICT 8

Ride South 123 #8

N

Scurry County · Wildcat field  · Directional

Ride South 123 #8 (API 42-415-34755) is a well in Scurry County operated by Murphy Bill W. Operating CO Inc, completed August 21, 2012.

The RRC has issued 2 drilling permits between 2012 and 2013, permitted to 7,300 ft.

Completion filings report 5 formation tops, including San Andres, Clear Fork, Wolfcamp, Cisco.

Its 2 leases have reported 44.2K barrels of oil and 17 mcf of gas since April 1993, last reporting in July 2026. The leases carry 8 wells, so these are lease totals, not this well alone.

Operator of record

Murphy Bill W. Operating Co Inc

Richardson, TX · P-5 Y, filed Oct 4, 2025 · 22 permits on file · (469) 222-7923

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMurphy Bill W. Operating Co Inc
Production reportsMurphy, Bill W. Operating Co,incthrough Apr 2026
Latest permitMurphy, Bill W. Operating Co,incOct 4, 2013
7,300
total depth, ft
2
permits on file
Oct 4, 2013
last permit issued
Aug 21, 2012
completed
44.2K
cumulative oil, bbl
17
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Aug 21, 2012
Shut in
—
Plugged
—

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
Sterling, T. J. O-11-67071Sharon Ridge (Clear Fork)Murphy, Bill W. Operating Co,inc744.2K17Apr 1993 – Jul 2026
Ride, South 123 O-11-69972WildcatMurphy, Bill W. Operating Co,inc100Aug 2012 – Nov 2014

Oil, barrels lease total

Last 12 months 783 · prior 12 936(-16%)

0100200202420252026

Chain of custody

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

  1. 1Thompson, J. CleoApr 1993 → Dec 2002
  2. 2Murphy, Bill W. Operating Co,incJan 2003 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
764872-99RecompletionMurphy, Bill W. Operating Co,incJun 18, 2013Oct 4, 2013Oct 31, 20133,650
728341-99DrillSharp Image Energy, Inc.Nov 15, 2011Jan 4, 2012Jul 19, 20127,300

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-11-67071————
—— O-11-69972————

Formation tops

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

FormationMD ftSubsea
San Andres1,800434
Clear Fork2,980-746
WolfcampWOLFCAMP SHALE4,910-2,676
CiscoCISCO LIME5,790-3,556
Canyon6,791-4,557

Perforations

Perforated and open-hole intervals.

FromToType
3,5863,640Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37542217.5420 S
8.6253,30911540 S
5.53,6507.875460 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
00Nov 12, 2014Feb 26, 2014—
00May 13, 2013Oct 11, 2012Yes

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