WELL · 42-415-34492 · DISTRICT 8

Ringo #1

Y

Scurry County · Earnest (6500 Sand) field · Producing  · Horizontal

Ringo #1 (API 42-415-34492) is a horizontal well in Scurry County operated by Raw Oil & Gas Inc., completed March 16, 2009 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended twice), issued November 14, 2008, permitted to 8,000 ft.

Completion filings report 6 formation tops, including San Andres, Clear Fork, Wolfcamp, Canyon.

Its lease has reported 99.4K barrels of oil and 341K mcf of gas since March 2009, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Raw Oil & Gas Inc.

Lubbock, TX · P-5 Y, filed Nov 4, 2025 · 148 permits on file · (806) 239-3443

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleRaw Oil & Gas Inc.
Production reportsRaw Oil & Gas, Inc.through Apr 2026
Latest permitRaw Oil & Gas, Inc.Nov 14, 2008
8,000
total depth, ft
3
permits on file
Nov 14, 2008
last permit issued
Mar 16, 2009
completed
99.4K
cumulative oil, bbl
341K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2009 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Mar 16, 2009
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Ringo O-11-69376Earnest (6500 Sand)Raw Oil & Gas, Inc.299.4K341KMar 2009 – Jul 2026

Oil, barrels lease total

Last 12 months 2,074 · prior 12 1,683(+23%)

0100200300202420252026

Gas, mcf lease total

Last 12 months 10,370 · prior 12 8,415(+23%)

05001K1.5K202420252026

Chain of custody

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

  1. 1Raw Oil & Gas, Inc.Mar 2009 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
674619-97DrillRaw Oil & Gas, Inc.Mar 4, 2009Nov 14, 2008Dec 12, 20088,000
674619-98DrillRaw Oil & Gas, Inc.Dec 5, 2008Nov 14, 2008—8,000
674619-99DrillRaw Oil & Gas, Inc.Nov 7, 2008Nov 14, 2008Dec 10, 20087,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-11-69376————

Formation tops

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

FormationMD ftSubsea
San Andres1,370937
Clear ForkCLEARFORK2,22582
Wolfcamp4,110-1,803
CanyonCANYON SAND6,996-4,689
Strawn7,170-4,863
Ellenburger7,638-5,331

Perforations

Perforated and open-hole intervals.

FromToType
7,25811,100Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,71512.25950 S
77,2588.751,080 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
00Jun 10, 2009Apr 28, 2009Yes
00May 27, 2009——

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