WELL · 42-165-38895 · DISTRICT 8

Denver Unit #6845

Y

Gaines County · Wasson field · Producing  · Directional

Denver Unit #6845 (API 42-165-38895) is a well in Gaines County operated by Occidental Permian Ltd., completed May 5, 2024 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued July 28, 2023, permitted to 5,900 ft.

Completion filings report 10 formation tops, including Yates, Seven Rivers, Queen, San Andres.

Its lease has reported 352M barrels of oil and 1.17B mcf of gas since January 1993, last reporting in July 2026. The lease carries 2,471 wells, so these are lease totals, not this well alone.

Operator of record

Occidental Permian Ltd.

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Feb 2, 2026
Permits on file
6,251
Phone
(713) 215-7000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOccidental Permian Ltd.
Production reportsOccidental Permian Ltd.through Apr 2026
Latest permitOccidental Permian Ltd.Jul 28, 2023
5,900
total depth, ft
1
permits on file
Jul 28, 2023
last permit issued
May 5, 2024
completed
352M
cumulative oil, bbl
1.17B
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 5, 2024
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

Surface location

32.948578, -102.785128

Google Maps ↗

Permit surface location from the RRC GIS record, in Gaines 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; they carry 2,471 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Denver Unit O-11-18910WassonOccidental Permian Ltd.2,471352M1.17BJan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 6,889,269 · prior 12 7,061,574(-2%)

0500K1M202420252026

Gas, mcf lease total

Last 12 months 9,464,854 · prior 12 11,150,167(-15%)

0500K1M1.5M202420252026

Chain of custody

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

  1. 1Shell Western E&P Inc.Jan 1993 → Feb 1997
  2. 2Altura Energy Ltd.Mar 1997 → Apr 2000
  3. 3Occidental Permian Ltd.May 2000 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
892463-99DrillOccidental Permian Ltd.Jul 27, 2023Jul 28, 2023Dec 8, 20235,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-11-18910————

Formation tops

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

FormationMD ftSubsea
YatesYATES - OVERPRESSURE, INERT GAS2,985521
Seven Rivers3,217289
Queen3,754-248
San AndresSAN ANDRES - ACTIVE CO2 FLOOD4,446-940
Clear ForkCLEARFORK——
Glorieta——
Leonard——
San Angelo——
Spraberry——
Wichita-AlbanyWICHITA ALBANY——

Perforations

Perforated and open-hole intervals.

FromToType
5,0555,164Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,22113.51,015 S
5.55,4298.751,890 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
00Sep 24, 2024Sep 4, 2024Yes

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.

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 neighbors, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Denver Unit42-165-38897

0.0 KM · Occidental Permian Ltd. · Section with this well →

Yates2,999
Seven Rivers3,201
Queen3,787
San Andres4,468
Wichita-Albany—
San Angelo—
Leonard—
Spraberry—

10 TOPS · FIRST 8

Denver Unit42-165-38899

0.0 KM · Occidental Permian Ltd. · Section with this well →

Yates3,010
Seven Rivers3,194
Queen3,815
San Andres4,505
Spraberry—
Leonard—
Glorieta—
Clear Fork—

10 TOPS · FIRST 8

Denver Unit42-165-38896

0.0 KM · Occidental Permian Ltd. · Section with this well →

Rustler2,1771,329
Yates3,004502
Seven Rivers3,232274
Queen3,841-335
San Andres4,458-952
Glorieta—
Wichita-Albany—
Spraberry—

10 TOPS · FIRST 8

Denver Unit42-165-00843

0.3 KM · Occidental Permian Ltd. · Section with this well →

Grayberg4,150-625
San Andres4,430-905
Goc4,850-1,325

Denver Unit42-165-38892

0.3 KM · Occidental Permian Ltd. · Section with this well →

Rustler2,1741,333
Yates3,002505
Seven Rivers3,231276
Queen3,828-321
Grayburg4,215-708
San Andres4,455-948
Clear Fork—
Wichita-Albany—

10 TOPS · FIRST 8

Denver Unit42-165-38893

0.3 KM · Occidental Permian Ltd. · Section with this well →

Yates3,009492
Yates3,009492
Seven Rivers3,227274
Queen3,845-344
San Andres4,476-975
San Andres4,476-975
Leonard—
Clear Fork—

13 TOPS · FIRST 8

Denver Unit42-165-38891

0.3 KM · Occidental Permian Ltd. · Section with this well →

Rustler2,1751,331
Yates3,001505
Seven Rivers3,218288
Queen3,824-318
Grayburg4,209-703
San Andres4,434-928
Clear Fork—
Wichita-Albany—

10 TOPS · FIRST 8

Denver Unit42-165-38894

0.3 KM · Occidental Permian Ltd. · Section with this well →

Yates3,001499
Seven Rivers3,237263
Queen3,806-306
San Andres4,498-998
San Angelo—
Clear Fork—
Glorieta—
Wichita-Albany—

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