TEXAS · WELLS · RUSK COUNTY · WILLIAMS, GLEN ESTATE GAS UNIT LEASE · API 42-401-34242 · DISTRICT 06

Williams Glen Estate Gas Unit #5

On schedule

Rusk County · Oak Hill (Cotton Valley) field · Producing  · Vertical

Williams Glen Estate Gas Unit #5 (API 42-401-34242) is a well in Rusk County operated by Tgnr East Texas LLC, completed May 31, 2007 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued March 8, 2007, permitted to 11,225 ft.

It was permitted by Anadarko E&P Company LP and has since transferred to Tgnr East Texas LLC on the wellbore schedule.

Completion filings report 5 formation tops, including Cnvl, Rsby, Sxtn, Tylr.

Its lease has reported 2.05K barrels of oil and 416K mcf of gas since May 2007, last reporting volume in August 2026.

Operator of record

TGNR East Texas LLC

Permitted by Anadarko E&P Company LP; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Feb 4, 2026
Permits on file
41
Phone
(346) 308-2250

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleTGNR East Texas LLC
Production reportsTGNR East Texas LLCthrough Apr 2026
Latest permitAnadarko E&P Company LPMar 8, 2007

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

11,225
total depth, ft
2
permits on file
Mar 8, 2007
last permit issued
May 31, 2007
completed
2.05K
cumulative oil, bbl
416K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · MAY 2007 THROUGH AUG 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 31, 2007
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH AUG 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Williams, Glen Estate Gas Unit G-6-230599Oak Hill (Cotton Valley)TGNR East Texas LLC12.05K416KMay 2007 – Aug 2026

Gas, mcf lease total

Last 12 months 1,694 · prior 12 5,630(-70%)

05001K1.5K202420252026

Wells named Williams Glen Estate Gas Unit

TGNR East Texas LLC's other wells filed under this lease name in Rusk County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Chain of custody

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

  1. 1Anadarko E&P Company LPMay 2007 → Dec 2012
  2. 2Anadarko E&P Onshore LLCJan 2013 → Nov 2016
  3. 3Cci East Texas Upstream LLCDec 2016 → Jan 2021
  4. 4TGNR East Texas LLCFeb 2021 → Aug 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
633201-98DrillAnadarko E&P Company LPSep 20, 2007Mar 8, 2007Apr 26, 200711,225
633201-99DrillAnadarko E&P Company LPFeb 7, 2007Mar 8, 2007Apr 26, 200711,000

Completions

CompletedLeaseFieldOperatorStatusDepth
May 31, 2007Williams Glen Estate Gas Unit G-6-230599Oak Hill (Cotton Valley)TGNR East Texas LLCProducing11,225

Formation tops

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

FormationMD ftSubsea
Cnvl9,427-8,950
Rsby10,443-9,966
Sxtn10,549-10,072
Tylr10,756-10,279
Bshl11,014-10,537

Perforations

Perforated and open-hole intervals.

FromToType
10,89210,902Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,21012.25450 S
5.511,2258.751,439 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Nov 13, 2007Aug 28, 2007Yes
00Nov 6, 2007——

Well logs

1 log loaded from the RRC's log index, the latest received Apr 8, 2008. Neutron. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
Neutron PorosityPULSED NEUTRON DECAY LOGSpans Cnvl, Rsby, Sxtn, Tylr, BshlTIFF5,000 to 11,225Apr 8, 2008run May 21, 2007—

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it.

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