WELL · 42-413-33034 · DISTRICT 9

Simmons #2

Plugged

Schleicher County · Wildcat field  · Vertical

Simmons #2 (API 42-413-33034) is a plugged well in Schleicher County, plugged December 19, 2025, last operated by VX Operating LLC.

The RRC has issued one drilling permit, issued October 20, 2025, permitted to 4,100 ft.

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

Operator of record

VX Operating LLC

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

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitVX Operating, LLCOct 20, 2025

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

4,100
total depth, ft
1
permits on file
Oct 20, 2025
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
Dec 19, 2025

Surface location

30.887966, -100.133137

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Schleicher 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
911210-99DrillVX Operating, LLCOct 16, 2025Oct 20, 2025Nov 12, 20254,100

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 →

McGregor Unit42-413-32981

5.2 KM · Boaz Energy II Operating, LLC · Section with this well →

Coleman Junction1,2001,114
Wolfcamp1,974340
Canyon3,750-1,436
Lime 41503,952-1,638
Strawn4,408-2,094
Ellenburger4,796-2,482
Cambrian5,540-3,226
Clear Fork—

9 TOPS · FIRST 8

Thornburg 2742-413-32989

5.6 KM · Boaz Energy II Operating, LLC · Section with this well →

Coleman Junction1,570658
Wolfcamp2,042186
Canyon3,618-1,390
Strawn3,908-1,680
Ellenburger—
San Angelo—
Clear Fork—

Thornburg 2742-413-33003

5.6 KM · Boaz Energy II Operating, LLC · Section with this well →

Coleman Junction1,378832
Wolfcamp2,027183
Canyon3,648-1,438
Strawn3,906-1,696
Ellenburger—
San Angelo—
Clear Fork—

Thornburg 2742-413-32999

5.7 KM · Boaz Energy II Operating, LLC · Section with this well →

Coleman Junction1,422
Wolfcamp2,058
Canyon3,926
Strawn4,302
San Angelo—
Ellenburger—
Clear Fork—

Thornburg 2742-413-31378

5.8 KM · McCabe, John Q. · Section with this well →

Palo Pinto3,748-1,520
Canyon4,197-1,969
Strawn4,318-2,090
Straw Lime4,318-2,090

Thornburg 2742-413-33006

5.9 KM · Boaz Energy II Operating, LLC · Section with this well →

Coleman Junction1,366867
Wolfcamp2,038195
Canyon3,664-1,431
Strawn3,904-1,671
Ellenburger—
San Angelo—
Clear Fork—

Thornburg 2742-413-32998

5.9 KM · Boaz Energy II Operating, LLC · Section with this well →

Coleman Junction1,328893
Wolfcamp2,428-207
Canyon3,710-1,489
Strawn3,977-1,756
Clear Fork—
Ellenburger—
San Angelo—

McGregor Unit42-413-32747

6.3 KM · Telesis Operating Co., Inc. · Section with this well →

Gunsight2,651-361
Adams Branch3,792-1,502
Palo Pinto4,227-1,937

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