WELL · 42-301-37163 · DISTRICT 8

Constrictor 53-35 V #W303HB

Y

Loving County · Phantom (Wolfcamp) field · Shut IN  · Horizontal

Constrictor 53-35 V #W303HB (API 42-301-37163) is a horizontal well in Loving County operated by Petro-Hunt Permian LLC, completed April 19, 2025 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit, issued October 25, 2024, permitted to 12,447 ft.

Completion filings report 10 formation tops, including Delaware, Cherry Canyon, Brushy Canyon, Bone Spring.

No lease production has been reported under this well’s leases.

Operator of record

Petro-Hunt Permian LLC

Dallas, TX · P-5 Y, filed Dec 4, 2025 · 250 permits on file · (432) 251-2097

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePetro-Hunt Permian LLC
Production reportsPetro-Hunt Permian, LLCthrough Apr 2026
Latest permitPetro-Hunt Permian, LLCOct 25, 2024
12,447
total depth, ft
1
permits on file
Oct 25, 2024
last permit issued
Apr 19, 2025
completed
0
cumulative oil, bbl
52.3K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2025 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 19, 2025
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

31.794050, -103.517976

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Loving 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
Constrictor 53-35 V G-10-300563Phantom (Wolfcamp)Petro-Hunt Permian, LLC1052.3KApr 2025 – Jul 2026

Gas, mcf lease total

Last 12 months 52,338 · prior 12 0

020K40K60K202420252026

Chain of custody

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

  1. 1Petro-Hunt Permian, LLCApr 2026 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
903531-99DrillPetro-Hunt Permian, LLCOct 24, 2024Oct 25, 2024Feb 22, 202512,447

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-10-300563————

Formation tops

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

FormationMD ftSubsea
Delaware4,748-1,854
Cherry Canyon5,732-2,838
Brushy Canyon6,900-4,006
Bone Spring8,382-5,488
3RD BS (Phantom Top)10,737-7,843
Wolfcamp11,330-8,436
Bell Canyon——
Pennsylvanian——
Red Bluff——
Strawn——

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3751,13017.5998 S
9.6259,01712.252,259 S
5.520,3166.752,876 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
00Dec 18, 2025Oct 3, 2025Yes

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 →

Constrictor 53-35 U42-301-37162

0.0 KM · Petro-Hunt Permian, LLC · Section with this well →

Delaware4,744-1,851
Cherry Canyon5,726-2,833
Brushy Canyon8,166-5,273
Bone Spring8,388-5,495
3RD BS (Phantom Top)10,724-7,831
Wolfcamp11,321-8,428
Red Bluff—
Pennsylvanian—

10 TOPS · FIRST 8

Constrictor 53-35 W42-301-37164

0.0 KM · Petro-Hunt Permian, LLC · Section with this well →

Delaware4,747-1,854
Cherry Canyon5,726-2,833
Brushy Canyon6,907-4,014
Bone Spring8,395-5,502
3RD BS (Phantom Top)10,741-7,848
Wolfcamp11,341-8,448
Pennsylvanian—
Red Bluff—

10 TOPS · FIRST 8

Constrictor 53-35 S42-301-37160

0.0 KM · Petro-Hunt Permian, LLC · Section with this well →

Delaware4,745-1,853
Cherry Canyon5,727-2,835
Brushy Canyon6,903-4,011
Bone Spring8,385-5,493
3RD BS (Phantom Top)10,710-7,818
Wolfcamp11,311-8,419
Strawn—
Red Bluff—

10 TOPS · FIRST 8

Constrictor 53-35 T42-301-37161

0.0 KM · Petro-Hunt Permian, LLC · Section with this well →

Delaware4,751-1,857
Cherry Canyon5,728-2,834
Brushy Canyon6,917-4,023
Bone Spring8,385-5,491
3RD BS (Phantom Top)10,721-7,827
Wolfcamp11,324-8,430
Strawn—
Red Bluff—

10 TOPS · FIRST 8

Constrictor 53-35 Q42-301-37158

0.0 KM · Petro-Hunt Permian, LLC · Section with this well →

Lamar4,717-1,824
Delaware4,745-1,852
Brushy Canyon6,898-4,005
Bone Spring8,365-5,472
3RD BS (Phantom Top)10,700-7,807
Red Bluff—
Wolfcamp—
Pennsylvanian—

10 TOPS · FIRST 8

Dimmit 53-3842-301-32076

0.1 KM · Petro-Hunt Permian, LLC · Section with this well →

Cherry Canyon3,700-809
Red Bluff3,900-1,009
Delaware4,695-1,804
Bell Canyon4,700-1,809
Brushy Canyon7,180-4,289
Bone Spring8,400-5,509
Bone Spring10,996-8,105
Wolfcamp11,305-8,414

12 TOPS · FIRST 8

Dimmit 53-3842-301-31777

0.3 KM · Petro-Hunt Permian, LLC · Section with this well →

Bone Spring11,039-8,147
A Sand11,208-8,316
Wolfcamp11,208-8,316
Wolfcamp11,488-8,596
Y Sand11,488-8,596

Constrictor 53-35 X42-301-37143

0.3 KM · Petro-Hunt Permian, LLC · Section with this well →

Delaware4,733-1,844
Cherry Canyon5,714-2,825
Brushy Canyon6,896-4,007
Bone Spring8,382-5,493
Red Bluff—
2ND BS—
Pennsylvanian—
Bell Canyon—

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