WELL · 42-447-36866 · DISTRICT 8

Matthews 23 #8

N

Throckmorton County  · Vertical

Matthews 23 #8 (API 42-447-36866) is a permitted well in Throckmorton County filed by Subsea Operating CO.; no completion report is on file yet.

The RRC has issued one drilling permit, issued July 8, 2025, permitted to 1,700 ft.

Operator of record

Subsea Operating Co.

Albany, TX · P-5 Y, filed Dec 4, 2025 · 40 permits on file · (325) 338-1699

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitSubsea Operating Co.Jul 8, 2025
1,700
total depth, ft
1
permits on file
Jul 8, 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
—

Surface location

32.994139, -99.360996

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Throckmorton 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
909020-99DrillSubsea Operating Co.Jul 1, 2025Jul 8, 2025—1,700

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). 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 →

Matthews 2342-447-36859

0.1 KM · Subsea Operating Co. · Section with this well →

Coleman Junction517946
Tannehill1,073390
Cook - Disposal1,216247
San Andres—
Wolfcamp—
Swastika - Disposal—
Sunsight - Disposal—
Flippen - Disposal—

10 TOPS · FIRST 8

Matthews QA42-447-36855

0.1 KM · Petex · Section with this well →

Coleman Junction597929
Saddle Creek1,118408
Cook - Disposal1,202324
Swastika - Disposal—
San Andres—
Permian (undifferentiated)—
Frye - Disposal—
Flippen - Disposal—

10 TOPS · FIRST 8

Matthews 2342-447-36841

0.2 KM · Subsea Operating Co. · Section with this well →

Coleman Junction428951
Cook - Disposal1,130249
Frye - Disposal—
Permian (undifferentiated)—
San Andres—
Sunsight - Disposal—
Swastika - Disposal—
Wolfcamp—

10 TOPS · FIRST 8

Matthews 75D42-447-36832

0.2 KM · Subsea Operating Co. · Section with this well →

Coleman Junction452946
Cook - Disposal1,144254
Cisco—
Flippen - Disposal—
Frye - Disposal—
Permian (undifferentiated)—
San Andres—
Sunsight - Disposal—

10 TOPS · FIRST 8

Matthews 2342-447-36862

0.3 KM · Subsea Operating Co. · Section with this well →

Coleman Junction494950
Cook - Disposal1,194250
Swastika - Disposal—
Sunsight - Disposal—
San Andres—
Cisco—
Frye - Disposal—
Flippen - Disposal—

10 TOPS · FIRST 8

Matthews QA42-447-36854

0.3 KM · Petex · Section with this well →

Coleman Junction560928
Saddle Creek1,081407
Cook - Disposal1,163325
Wolfcamp—
San Andres—
Sunsight - Disposal—
Flippen - Disposal—
Permian (undifferentiated)—

10 TOPS · FIRST 8

Matthews 75D42-447-36807

0.3 KM · Subsea Operating Co. · Section with this well →

Coleman Junction410960
Cook - Disposal1,096274
Permian (undifferentiated)—
Cisco—
Wolfcamp—
Swastika - Disposal—
Sunsight - Disposal—
San Andres—

10 TOPS · FIRST 8

Matthews 2342-447-36850

0.3 KM · Subsea Operating Co. · Section with this well →

Coleman Junction452945
Cook - Disposal1,141256
Cisco—
Flippen - Disposal—
Frye - Disposal—
Permian (undifferentiated)—
San Andres—
Wolfcamp—

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