WELL · 42-073-31056 · DISTRICT 6

Reklaw GU 4 #9

N

Cherokee County  · Vertical

Reklaw GU 4 #9 (API 42-073-31056) is a permitted well in Cherokee County filed by Erebor Resources, LLC; no completion report is on file yet.

The RRC has issued 3 drilling permits (amended once) between 2003 and 2018, permitted to 12,000 ft.

Completion filings report 5 formation tops, including Massive Anhydrite (marker), Rodessa, James Lime, Pettit.

Operator of record

Erebor Resources, LLC

Tyler, TX · P-5 Y, filed Aug 2, 2019 · 3 permits on file · (936) 634-1020

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsGreat American Resources Inc.through Feb 2026
Latest permitErebor Resources, LLCFeb 9, 2018
12,000
total depth, ft
4
permits on file
Feb 9, 2018
last permit issued
—
completed
0
cumulative oil, bbl
281K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2003 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

Surface location

31.767122, -94.980420

OpenStreetMap → ·  Google Maps →

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

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Reklaw Gas Unit 4 G-6-197153Reklaw (Travis Peak)Great American Resources Inc.10115KAug 2003 – Jul 2026
Reklaw GU 4 G-6-264148Reklaw (Rodessa)Great American Resources Inc.10166KSep 2011 – Jul 2026

Gas, mcf lease total

Last 12 months 696 · prior 12 1,009(-31%)

050100150202420252026

Chain of custody

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

  1. 1Samson Lone Star LPAug 2003 → Nov 2005
  2. 2Lime Rock Resources a, L.P.Dec 2005 → Nov 2011
  3. 3Lre Operating, LLCDec 2011 → Sep 2015
  4. 4Vanguard Operating, LLCOct 2015 → Aug 2016
  5. 5Proex Energy Management, L.L.C.Sep 2016 → Nov 2016
  6. 6Erebor Resources, LLCDec 2016 → Aug 2019
  7. 7Western Energy Group, LLCNov 2019 → Jun 2020
  8. 8Crisco Operating LLCJul 2020 → Sep 2020
  9. 9Falcon Production LLCOct 2020 → Mar 2022
  10. 10Nec Operating, LLCDec 2022 → Jul 2025
  11. 11Great American Resources Inc.Aug 2025 → Feb 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
836092-99RecompletionErebor Resources, LLCFeb 7, 2018Feb 9, 2018—9,000
720988-99RecompletionLime Rock Resources a, L.P.Jul 26, 2011Aug 3, 2011Sep 19, 20119,640
528883-98DrillSamson Lone Star LPMay 22, 2003Mar 28, 2003Jun 7, 200312,000
528883-99DrillSamson Lone Star LPFeb 26, 2003Mar 28, 2003—12,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-6-197153————
—— G-6-264148————

Formation tops

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

FormationMD ftSubsea
Massive Anhydrite (marker)MASSIVE ANHYDRITE7,560-7,240
Rodessa7,743-7,423
Rodessa7,800-7,480
James LimeJAMES8,232-7,912
James Lime8,232-7,912
James Lime8,270-7,950
Pettit8,470-8,150
Travis Peak8,933-8,613

Perforations

Perforated and open-hole intervals.

FromToType
7,7857,791Perforated
7,9427,955Perforated
8,9339,198Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,20412.25925 S
4.59,6438.75810 S
4.59,6437.8751,210 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
00Apr 10, 2019Aug 17, 2018—
00Nov 13, 2012Nov 10, 2011—
00Feb 9, 2004Jan 5, 2004—
00Oct 30, 2003Sep 18, 2003Yes
00Oct 21, 2003——

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 6 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 →

Wade GU 142-073-31059

3.0 KM · Samson Lone Star LP · Section with this well →

Rodessa7,768-7,427
James Lime8,258-7,917
Pettit8,494-8,153

Wade GU 142-073-31024

3.6 KM · Samson Lone Star LP · Section with this well →

Woodbine4,580-4,304
Massive Anhydrite (marker)7,500-7,224
Rodessa7,606-7,330
James Lime8,236-7,960
Pettit8,482-8,206
Pettit8,560-8,284
Travis Peak8,876-8,600

Vallier-Sessions42-073-31589

4.5 KM · Maximus Operating, Ltd. · Section with this well →

Nacatoch3,120-2,787
Woodbine4,459-4,126
Paluxy5,809-5,476
Glen Rose6,087-5,754
Rodessa7,816-7,483
James Lime8,306-7,973
Cotton Valley11,130-10,797
Bossier12,348-12,015

9 TOPS · FIRST 8

Mary Kate G.U. 142-073-31001

4.6 KM · Samson Lone Star LP · Section with this well →

Massive Anhydrite (marker)7,630-7,304
Rodessa7,800-7,474
James Lime8,333-8,007
Pine Island Shale8,476-8,150
Pine Island8,490-8,164
Pettit8,580-8,254
Pettit8,580-8,254
Travis Peak9,000-8,674

14 TOPS · FIRST 8

Paxton GU 142-073-31201

15.5 KM · Samson Lone Star LP · Section with this well →

Austin Chalk5,170-4,702
Glen Rose5,170-4,702
Rodessa8,835-8,367
James Lime9,360-8,892
Pettit9,630-9,162

Mandy GU 142-073-31022

15.8 KM · Samson Lone Star LP · Section with this well →

Woodbine5,081-4,642
Rodessa8,710-8,271
James Lime9,230-8,791
Pettit9,500-9,061

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