WELL · 42-371-40037 · DISTRICT 8

Roosterfish Unit 22SE83 #83H

Y

Pecos County · Wolfbone (Trend Area) field · Producing  · Horizontal

Roosterfish Unit 22se83 #83H (API 42-371-40037) is a horizontal well in Pecos County operated by Vtx Energy Operating LLC, completed November 27, 2019 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued March 29, 2019, permitted to 13,000 ft.

It was permitted by Pri Operating, LLC and has since transferred to Vtx Energy Operating LLC on the wellbore schedule.

Completion filings report 10 formation tops, including Glorieta, Grayburg, O'Brien, Queen.

Its lease has reported 240K barrels of oil and 555K mcf of gas since September 2019, last reporting in July 2026.

Operator of record

VTX Energy Operating LLC

Permitted by Pri Operating, LLC; the EWA schedule now lists a different operator.

Austin, TX · P-5 Y, filed May 4, 2026 · 164 permits on file · (800) 826-8119

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleVTX Energy Operating LLC
Production reportsVTX Energy Operating, LLCthrough Apr 2026
Latest permitPri Operating, LLCMar 29, 2019

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

13,000
total depth, ft
2
permits on file
Mar 29, 2019
last permit issued
Nov 27, 2019
completed
240K
cumulative oil, bbl
555K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2019 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Nov 27, 2019
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

31.205739, -103.127935

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Pecos 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
Roosterfish Unit 22SE83 O-10-53032Wolfbone (Trend Area)VTX Energy Operating, LLC1240K555KSep 2019 – Jul 2026

Oil, barrels lease total

Last 12 months 20,102 · prior 12 24,761(-19%)

02K4K202420252026

Gas, mcf lease total

Last 12 months 73,486 · prior 12 109,963(-33%)

05K10K15K202420252026

Chain of custody

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

  1. 1Pri Operating, LLCSep 2019 → Jun 2023
  2. 2VTX Energy Operating, LLCSep 2023 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
851571-98DrillPri Operating, LLCMay 7, 2019Mar 29, 2019Jun 13, 201913,000
851571-99DrillPri Operating, LLCMar 28, 2019Mar 29, 2019—13,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-53032————

Formation tops

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

FormationMD ftSubsea
Glorieta——
Grayburg——
O'Brien——
Queen——
Rustler——
Seven Rivers——
Soma——
Toborg——
Tubb——
Yates——

Perforations

Perforated and open-hole intervals.

FromToType
10,76118,049Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3751,63517.51,442 S
9.6259,73112.251,839 S
5.518,0498.52,285 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, 2020Jan 22, 2020Yes
00Feb 28, 2020Nov 12, 2019Yes

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 →

Roosterfish Unit 22SE6342-371-40038

0.0 KM · Pri Operating, LLC · Section with this well →

Glorieta—
Grayburg—
O'Brien—
Queen—
Rustler—
Seven Rivers—
Soma—
Toborg—

10 TOPS · FIRST 8

Roosterfish Unit 22SW42-371-39591

0.2 KM · Pri Operating, LLC · Section with this well →

Glorieta—
Grayburg—
O'Brien—
Queen—
Rustler—
Seven Rivers—
Soma—
Toborg—

10 TOPS · FIRST 8

Roosterfish Unit 22SW6342-371-40331

0.2 KM · Pri Operating, LLC · Section with this well →

San Andres—
Yates—
Toborg—
Soma—
Seven Rivers—
Capitan—
Rustler—
Queen—

10 TOPS · FIRST 8

Roosterfish Unit 22SW3342-371-40332

0.2 KM · Pri Operating, LLC · Section with this well →

Capitan—
Grayburg—
O'Brien—
Queen—
Rustler—
San Andres—
Seven Rivers—
Soma—

10 TOPS · FIRST 8

Roosterfish Unit 22SW3442-371-40334

0.3 KM · Pri Operating, LLC · Section with this well →

Yates—
Toborg—
Soma—
Seven Rivers—
San Andres—
Capitan—
Rustler—
Queen—

10 TOPS · FIRST 8

Roosterfish Unit 22SW6442-371-40333

0.3 KM · Pri Operating, LLC · Section with this well →

San Andres—
Capitan—
Grayburg—
O'Brien—
Queen—
Rustler—
Seven Rivers—
Soma—

10 TOPS · FIRST 8

Roosterfish Unit 22SW1642-371-40363

0.3 KM · Pri Operating, LLC · Section with this well →

Capitan—
Yates—
Toborg—
Soma—
Seven Rivers—
San Andres—
Rustler—
Queen—

10 TOPS · FIRST 8

Roosterfish Unit 22SE6442-371-40032

0.4 KM · Pri Operating, LLC · Section with this well →

Grayburg—
Yates—
Tubb—
Toborg—
Soma—
Seven Rivers—
Rustler—
Queen—

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