WELL · 42-235-36610 · DISTRICT 7

Tullos #1

Plugged

Irion County · Wildcat field  · Vertical

Tullos #1 (API 42-235-36610) is a plugged well in Irion County, plugged February 8, 2024, last operated by Rising Star Energy Ptr L.L.C..

The RRC has issued one drilling permit, issued January 19, 2024, permitted to 7,500 ft.

It was permitted by Rising Star Energy Ptr, L.L.C. and has since transferred to Rising Star Energy Ptr L.L.C. on the wellbore schedule.

Operator of record

Rising Star Energy PTR L.L.C.

Permitted by Rising Star Energy PTR, L.L.C.; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitRising Star Energy PTR, L.L.C.Jan 19, 2024

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

7,500
total depth, ft
1
permits on file
Jan 19, 2024
last permit issued
—
completed
—
cumulative oil, bbl
—
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
Feb 8, 2024

Surface location

31.444618, -100.749589

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Irion County.

Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
896619-99DrillRising Star Energy PTR, L.L.C.Jan 17, 2024Jan 19, 2024Jan 23, 20247,500

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 has no tops filed, so it cannot anchor a section; its neighbours can.

Section of the neighbours →

War Emblem42-235-36682

0.1 KM · Rising Star Energy PTR, L.L.C. · Section with this well →

San Andres7611,323
Clear Fork1,205879
Coleman Junction4,120-2,036
Wolfcamp4,605-2,521
Cisco5,790-3,706
Canyon6,409-4,325
Spraberry—
Fusselman—

9 TOPS · FIRST 8

Remagen Unit42-235-36686

0.2 KM · Moriah Operating,llc · Section with this well →

San Andres4011,687
Clear Fork7901,298
Tubb1,133955
Wichita-Albany2,638-550
Cisco4,963-2,875
Canyon6,493-4,405
Grayburg—
Fusselman—

10 TOPS · FIRST 8

Dunkirk Unit42-235-36618

1.8 KM · Moriah Operating,llc · Section with this well →

San Andres4001,667
Glorieta6991,368
Clear Fork7691,298
Tubb1,230837
Wichita-Albany2,626-559
Wolfcamp3,766-1,699
Canyon5,819-3,752
Spraberry—

10 TOPS · FIRST 8

Normandy Unit42-235-36664

2.5 KM · Moriah Operating,llc · Section with this well →

San Andres4001,675
Clear Fork7941,281
Wolfcamp3,902-1,827
Canyon6,327-4,252
Fusselman—
Spraberry—
Grayburg—

Dresden Unit42-235-36662

3.0 KM · Moriah Operating,llc · Section with this well →

San Andres3751,700
Clear Fork7691,306
Wolfcamp3,878-1,803
Canyon6,299-4,224
Spraberry—
Grayburg—
Fusselman—

Tullos42-235-36600

3.1 KM · Moriah Operating,llc · Section with this well →

Grayburg2431,834
San Andres3271,750
Clear Fork7171,360
Wolfcamp—
Spraberry—
Fusselman—
Canyon—

Tullos42-235-36576

3.1 KM · Moriah Operating,llc · Section with this well →

Grayburg2431,833
San Andres3271,749
Clear Fork7171,359
Wichita-Albany2,900-824
Spraberry—
Wolfcamp—
Fusselman—
Canyon—

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