TEXAS · WELLS · MIDLAND COUNTY · LEVERETT LEASE · API 42-329-38772 · DISTRICT 7B

Leverett #2615

Y

Midland County · Spraberry (Trend Area) field · Producing  · Vertical

Leverett #2615 (API 42-329-38772) is a well in Midland County operated by Permian Resources Operating LLC, completed September 7, 2023 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued June 24, 2013, permitted to 10,949 ft.

It was permitted by Resolute Natural Res. CO., LLC and has since transferred to Permian Resources Operating LLC on the wellbore schedule.

Completion filings report 9 formation tops, including Yates, San Andres, Clear Fork, Spraberry.

Its lease has reported 148K barrels of oil and 449K mcf of gas since August 2011, last reporting volume in April 2026. The lease carries 3 wells, so these are lease totals, not this well alone.

Operator of record

Permian Resources Operating LLC

Permitted by Resolute Natural Res. Co., LLC; the EWA schedule now lists a different operator.

Based in
Midland, TX
P-5 status
Active (A)
P-5 last filed
Nov 25, 2025
Permits on file
608
Phone
(432) 695-4222

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePermian Resources Operating LLC
Production reportsPermian Resources Operating, LLCthrough Apr 2026
Latest permitResolute Natural Res. Co., LLCJun 24, 2013

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

10,949
total depth, ft
2
permits on file
Jun 24, 2013
last permit issued
Sep 7, 2023
completed
148K
cumulative oil, bbl
449K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2011 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Sep 7, 2023
Shut in
—
Plugged
—

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

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 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Leverett O-10-41952Spraberry (Trend Area)Permian Resources Operating, LLC3148K449KAug 2011 – Apr 2026

Gas, mcf lease total

Last 12 months 13,253 · prior 12 17,395(-24%)

01K2K202420252026

Oil, barrels lease total

Last 12 months 1,387 · prior 12 2,476(-44%)

0200400600202420252026

Chain of custody

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

  1. 1RSP Permian, LLCSep 2011 → Mar 2013
  2. 2Resolute Natural Res. Co., LLCApr 2013 → Nov 2015
  3. 3Independence Resources Mgmt, LLCDec 2015 → Mar 2021
  4. 4Earthstone Operating, LLCApr 2021 → Oct 2023
  5. 5Permian Resources Operating, LLCNov 2023 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
764869-98DrillResolute Natural Res. Co., LLCJun 16, 2014Jun 24, 2013Jun 28, 201312,000
764869-99DrillResolute Natural Res. Co., LLCJun 18, 2013Jun 24, 2013Jun 28, 201311,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Sep 7, 2023Leverett O-10-41952Spraberry (Trend Area)Permian Resources Operating LLCProducing10,949

Formation tops

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

FormationMD ftSubsea
Yates3,060-129
San AndresSAN ANDREAS4,776-1,845
San Andres4,776-1,845
Clear Fork7,381-4,450
Clear ForkCLEARFORK7,381-4,450
Spraberry8,279-5,348
Dean9,401-6,470
Wolfcamp9,479-6,548
Cline10,245-7,314
Strawn10,599-7,668
Atoka10,844-7,913

Perforations

Perforated and open-hole intervals.

FromToType
8,60010,780Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37542017.5470 S
8.6255,50011710 S
5.510,9407.875830 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Oct 26, 2023Sep 13, 2023—
00Jul 23, 2014Jan 30, 2014Yes

Well logs

1 log loaded from the RRC's log index, the latest received Oct 28, 2014. Neutron. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
NEUTRON POROSITYSpans Yates, San Andres, Clear Fork, Spraberry, Dean, Wolfcamp, Cline, Strawn, AtokaTIFF4,000 to 10,857Oct 28, 2014run Jul 25, 20135.61

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it.

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