WELL · 42-475-36783 · DISTRICT 8

Rhino #1

N

Ward County · Quito South (Olds Delaware) field  · Vertical

Rhino #1 (API 42-475-36783) is a well in Ward County operated by Seaboard Operating CO., completed October 31, 2014.

The RRC has issued one drilling permit, issued July 11, 2014, permitted to 5,500 ft.

Completion filings report 10 formation tops, including Rustler, Delaware, Clear Fork, Glorieta.

Its 2 leases have reported 27K barrels of oil and 32.5K mcf of gas since October 2014, last reporting in July 2026. The leases carry 3 wells, so these are lease totals, not this well alone.

Operator of record

Seaboard Operating Co.

Based in
Midland, TX
P-5 status
Active – Extension (X)
P-5 last filed
Jun 9, 2026
Permits on file
189
Phone
(432) 684-7005

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSeaboard Operating Co.
Production reportsSeaboard Operating Co.through Apr 2026
Latest permitSeaboard Operating Co.Jul 11, 2014
5,500
total depth, ft
1
permits on file
Jul 11, 2014
last permit issued
Oct 31, 2014
completed
27K
cumulative oil, bbl
32.5K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2014 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 31, 2014
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 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Rhino O-10-46210Quito (Delaware-Consolidated)Seaboard Operating Co.225.5K31KMay 2015 – Jul 2026
Rhino O-10-45754Quito, South (Olds Delaware)Seaboard Operating Co.11.48K1.49KOct 2014 – Jul 2015

Oil, barrels lease total

Last 12 months 1,680 · prior 12 1,877(-10%)

0100200202420252026

Gas, mcf lease total

Last 12 months 1,725 · prior 12 2,235(-23%)

0100200300202420252026

Chain of custody

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

  1. 1Seaboard Operating Co.Nov 2014 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
789250-99DrillSeaboard Operating Co.Jun 11, 2014Jul 11, 2014Sep 12, 20145,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-45754————
—— O-10-46210————

Formation tops

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

FormationMD ftSubsea
Rustler1,1501,469
Delaware4,870-2,251
Clear ForkCLEARFORK——
Glorieta——
Holt——
Queen——
San AndresSAN ANDRES - HIGH FLOWS, H2S, CO——
Seven Rivers——
Tubb——
Yates——

Perforations

Perforated and open-hole intervals.

FromToType
4,8704,920Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,16812.25815 S
5.55,1187.875250 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 5, 2015Dec 15, 2014Yes
00Feb 19, 2015Dec 15, 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) 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/47536783, documented in the API reference.