TEXAS · WELLS · LOVING COUNTY · API 42-301-32313 · DISTRICT 7B

Bunin 4 #3H

Y

Loving County · Phantom (Wolfcamp) field · Producing  · Horizontal

Bunin 4 #3H (API 42-301-32313) is a horizontal well in Loving County operated by Wpx Energy Permian LLC, completed February 17, 2015 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued September 9, 2014, permitted to 10,435 ft.

It was permitted by Rki Exploration & Production LLC and has since transferred to Wpx Energy Permian LLC on the wellbore schedule.

Completion filings report 12 formation tops, including Bell Canyon, Cherry Canyon, Brushy Canyon, Bone Spring.

Its 2 leases have reported 480K barrels of oil and 1.92M mcf of gas since February 2014, last reporting volume in March 2026. The leases carry 8 wells, so these are lease totals, not this well alone.

Operator of record

WPX Energy Permian LLC

Permitted by RKI Exploration & Production LLC; the EWA schedule now lists a different operator.

Based in
Oklahoma City, OK
P-5 status
Active (A)
P-5 last filed
Oct 22, 2025
Permits on file
956
Phone
(405) 235-3611

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleWPX Energy Permian LLC
Production reportsWPX Energy Permian, LLCthrough Mar 2026
Latest permitRKI Exploration & Production LLCSep 9, 2014

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

10,435
total depth, ft
1
permits on file
Sep 9, 2014
last permit issued
Feb 17, 2015
completed
480K
cumulative oil, bbl
1.92M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2015 THROUGH Mar 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Feb 17, 2015
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 2 leases this well is completed on; they carry 8 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Bunin 4 G-10-285585Phantom (Wolfcamp)WPX Energy Permian, LLC1480K1.92MFeb 2015 – Mar 2026
Bunin 4 O-10-45742Phantom (Wolfcamp)WPX Energy Permian, LLC700Feb 2014 – —

Gas, mcf lease total

Last 12 months 108,770 · prior 12 135,559(-20%)

05K10K15K202420252026

Chain of custody

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

  1. 1WPX Energy Permian, LLCFeb 2015 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
794006-99DrillRKI Exploration & Production LLCAug 12, 2014Sep 9, 2014Sep 20, 201416,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Feb 17, 2015Bunin 4 G-10-285585Phantom (Wolfcamp)WPX Energy Permian LLCProducing10,435
Feb 17, 2015Bunin 4 O-10-45742Phantom (Wolfcamp)WPX Energy Permian LLCNot on Schedule—

Formation tops

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

FormationMD ftSubsea
Bell Canyon3,212-418
Cherry Canyon4,281-1,487
Brushy Canyon6,735-3,941
Bone SpringBONE SPRINGS7,020-4,226
Wolfcamp10,025-7,231
AtokaATOKA - HIGH PRESSURE——
Delaware——
Ellenburger——
Fusselman——
Pennsylvanian——
Red Bluff——
Strawn——

Perforations

Perforated and open-hole intervals.

FromToType
10,96514,787Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37595817.51,000 S
9.6253,13212.251,050 S
75,5168.75455 S
79,6548.75455 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
00Jan 30, 2019Dec 4, 2018Yes
00Jun 26, 2015Apr 6, 2015Yes

Well logs

2 logs loaded from the RRC's log index, 1 of them with a digital LAS file, the latest received Apr 23, 2019. Density, While drilling (MWD), 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
Measure While Drilling (MWD)Spans Bell Canyon, Cherry Canyon, Brushy Canyon, Bone Spring, WolfcampLAS + TIFF1,050 to 14,943Apr 23, 20191.09 + 10.8
NEUTRON/DENSITY POROSITYSpans Bell Canyon, Cherry Canyon, Brushy Canyon, Bone SpringTIFF100 to 9,666Nov 13, 2017run Oct 6, 20148.81

"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. The University Lands library has no per-well link: then paste it into its 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/30132313, documented in the API reference.