WELL · 42-317-45804 · DISTRICT 8

Kimberly N #1710WA

Y

Martin County · Spraberry (Trend Area) field · Producing  · Horizontal

Kimberly N #1710WA (API 42-317-45804) is a horizontal well in Martin County operated by Diamondback E&P LLC, completed October 7, 2024 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued January 9, 2024, permitted to 13,000 ft.

Completion filings report 11 formation tops, including Santa Rosa, Yates, Queen, Grayburg.

Its lease has reported 148K barrels of oil and 167K mcf of gas since June 2024, last reporting in July 2026.

Operator of record

Diamondback E&P LLC

Midland, TX · P-5 Y, filed Mar 4, 2026 · 5,237 permits on file · (855) 247-5920

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDiamondback E&P LLC
Production reportsDiamondback E&P LLCthrough Apr 2026
Latest permitDiamondback E&P LLCJan 9, 2024
13,000
total depth, ft
1
permits on file
Jan 9, 2024
last permit issued
Oct 7, 2024
completed
148K
cumulative oil, bbl
167K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2024 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 7, 2024
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

Surface location

32.145983, -102.172586

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Martin 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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Kimberly N O-10-61556Spraberry (Trend Area)Diamondback E&P LLC1148K167KJun 2024 – Jul 2026

Oil, barrels lease total

Last 12 months 57,177 · prior 12 91,060(-37%)

010K20K30K202420252026

Gas, mcf lease total

Last 12 months 70,407 · prior 12 96,509(-27%)

010K20K30K202420252026

Chain of custody

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

  1. 1Diamondback E&P LLCOct 2024 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
896128-99DrillDiamondback E&P LLCDec 21, 2023Jan 9, 2024Mar 28, 202413,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-61556————

Formation tops

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

FormationMD ftSubsea
Santa Rosa1,2321,687
Yates2,979-60
Queen3,722-803
Grayburg4,197-1,278
San AndresSAN ANDRES - ACTIVE CO2 FLOOD; H4,579-1,660
Clear ForkCLEARFORK7,006-4,087
Spraberry8,128-5,209
Dean9,363-6,444
Wolfcamp9,570-6,651
Cisco——
Pennsylvanian——

Perforations

Perforated and open-hole intervals.

FromToType
9,84220,223Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
11.751,98914.751,530 S
8.6258,680111,065 S
5.520,2737.8752,180 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
00Mar 24, 2025Feb 11, 2025—
00Oct 4, 2024Aug 14, 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 neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Kimberly J42-317-45801

0.0 KM · Diamondback E&P LLC · Section with this well →

Santa Rosa1,2321,687
Yates2,979-60
Queen3,722-803
Grayburg4,197-1,278
San Andres4,579-1,660
Clear Fork7,012-4,093
Spraberry8,115-5,196
Dean9,534-6,615

11 TOPS · FIRST 8

Kimberly G42-317-43447

0.0 KM · Diamondback E&P LLC · Section with this well →

Santa Rosa1,2321,687
Yates2,979-60
Queen3,722-803
Grayburg4,197-1,278
San Andres4,579-1,660
Clear Fork6,961-4,042
Spraberry8,136-5,217
Cisco—

11 TOPS · FIRST 8

Kimberly M42-317-45803

0.0 KM · Diamondback E&P LLC · Section with this well →

Dean—
Yates—
Wolfcamp—
Spraberry—
Santa Rosa—
San Andres—
Queen—
Pennsylvanian—

10 TOPS · FIRST 8

Kimberly L42-317-45802

0.0 KM · Diamondback E&P LLC · Section with this well →

Santa Rosa1,2321,687
Yates2,979-60
Queen3,722-803
Grayburg4,197-1,278
San Andres4,579-1,660
Clear Fork6,960-4,041
Spraberry8,132-5,213
Cisco—

10 TOPS · FIRST 8

Kimberly F42-317-43446

0.0 KM · Diamondback E&P LLC · Section with this well →

Santa Rosa1,2321,687
Yates2,979-60
Queen3,722-803
Grayburg4,197-1,278
San Andres4,579-1,660
Clear Fork6,960-4,041
Spraberry8,135-5,216
Cisco—

11 TOPS · FIRST 8

Kimberly O42-317-45844

0.2 KM · Diamondback E&P LLC · Section with this well →

Yates3,004-87
Queen3,734-817
Grayburg4,197-1,280
San Andres4,592-1,675
Spraberry8,121-5,204
Dean9,344-6,427
Wolfcamp9,555-6,638
Fusselman—

17 TOPS · FIRST 8

Kimberly K42-317-45843

0.2 KM · Diamondback E&P LLC · Section with this well →

Yates3,003-86
Queen3,731-814
Grayburg4,203-1,286
San Andres4,593-1,676
Clear Fork6,961-4,044
Spraberry8,113-5,196
Dean9,329-6,412
Wolfcamp9,543-6,626

12 TOPS · FIRST 8

Kimberly I42-317-45799

0.2 KM · Diamondback E&P LLC · Section with this well →

Yates3,003-86
Queen3,733-816
Grayburg4,205-1,288
San Andres4,596-1,679
Clear Fork6,973-4,056
Spraberry8,119-5,202
Wolfcamp—
Cisco—

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