WELL · 42-115-33818 · DISTRICT 10

Foxrun Unit #U 1H

N

Dawson County  · Horizontal

Foxrun Unit #U 1H (API 42-115-33818) is a permitted horizontal well in Dawson County filed by Cgs Operating, LLC; no completion report is on file yet.

The RRC has issued one drilling permit (amended twice), issued December 28, 2020, permitted to 10,100 ft.

Operator of record

CGS Operating, LLC

Kilgore, TX · P-5 Y, filed Jul 3, 2024 · 45 permits on file · (903) 571-5845

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitCGS Operating, LLCDec 28, 2020
10,100
total depth, ft
3
permits on file
Dec 28, 2020
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.630971, -102.043271

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Dawson 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
866610-97DrillCGS Operating, LLCJan 18, 2021Dec 28, 2020—10,100
866610-98DrillCGS Operating, LLCDec 28, 2020Dec 28, 2020—10,100
866610-99DrillCGS Operating, LLCDec 18, 2020Dec 28, 2020—9,000

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 →

Stonecreek Unit42-115-33817

1.2 KM · CGS Operating, LLC · Section with this well →

Yates2,768179
San Andres4,357-1,410
Clear Fork6,041-3,094
Spraberry7,837-4,890
Dean9,174-6,227
Canyon—
Wolfcamp—
Pennsylvanian—

10 TOPS · FIRST 8

Anderson42-115-34027

1.3 KM · Beach Exploration, Inc. · Section with this well →

Yates2,760191
San Andres4,680-1,729
Spraberry7,848-4,897
Lower Gin8,189-5,238
San Andres—
Wolfcamp—
Canyon—
Dean—

9 TOPS · FIRST 8

Rinewalt42-115-33774

1.7 KM · Halvey Energy, LLC · Section with this well →

Yates2,766200
San Andres3,770-804
Spraberry7,550-4,584
Silurian (undifferentiated)—
Pennsylvanian—
Mississippian—
Devonian—
Canyon—

10 TOPS · FIRST 8

Stonecreek a Unit42-115-33831

1.8 KM · CGS Operating, LLC · Section with this well →

Yates2,754192
San Andres4,298-1,352
Clear Fork6,024-3,078
Spraberry7,867-4,921
Canyon—
Wolfcamp—
Pennsylvanian—
Mississippian—

10 TOPS · FIRST 8

Stonecreek Unit42-115-33830

1.8 KM · CGS Operating, LLC · Section with this well →

Yates2,765155
San Andres4,280-1,360
Spraberry7,828-4,908
Wolfcamp—
Canyon—
Dean—
Devonian—
Mississippian—

10 TOPS · FIRST 8

Carr42-115-33824

1.8 KM · Halvey Energy, LLC · Section with this well →

Yates2,740218
San Andres4,038-1,080
Spraberry7,545-4,587
Devonian—
Mississippian—
Pennsylvanian—
Silurian (undifferentiated)—
Wolfcamp—

10 TOPS · FIRST 8

Carr42-115-33792

1.9 KM · Halvey Energy, LLC · Section with this well →

Yates2,768195
San Andres4,075-1,112
Spraberry7,555-4,592
Pennsylvanian—
Silurian (undifferentiated)—
Canyon—
Devonian—
Mississippian—

10 TOPS · FIRST 8

Carr42-115-33762

2.0 KM · Halvey Energy, LLC · Section with this well →

Yates2,778196
San Andres3,935-961
Spraberry7,550-4,576
Dean—
Canyon—
Wolfcamp—
Silurian (undifferentiated)—
Pennsylvanian—

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