WELL · 42-393-32489 · DISTRICT 10

Chambers 9 #2

Y

Roberts County · St. Clair (Granite Wash) field · Shut IN  · Vertical

Chambers 9 #2 (API 42-393-32489) is a well in Roberts County operated by Texakoma E & P LLC, completed March 24, 2013 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit, issued November 26, 2012, permitted to 8,990 ft.

Completion filings report 3 formation tops, including Brown Dolomite, Kansas City, Des Moines.

Its lease has reported 102K barrels of oil and 195K mcf of gas since March 2013, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Texakoma E & P LLC

Based in
Plano, TX
P-5 status
Active – Extension (X)
P-5 last filed
Nov 24, 2025
Permits on file
102
Phone
(972) 701-9106

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleTexakoma E & P LLC
Production reportsTexakoma E & P, LLCthrough Apr 2026
Latest permitTexakoma E & P, LLCNov 26, 2012
8,990
total depth, ft
1
permits on file
Nov 26, 2012
last permit issued
Mar 24, 2013
completed
102K
cumulative oil, bbl
195K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2013 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Mar 24, 2013
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active – Extension (X)

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.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Chambers 9 O-14-9081St. Clair (Granite Wash)Texakoma E & P, LLC2102K195KMar 2013 – Jul 2026

Oil, barrels lease total

Last 12 months 2,204 · prior 12 2,826(-22%)

0100200300202420252026

Gas, mcf lease total

Last 12 months 970 · prior 12 1,222(-21%)

0100200300202420252026

Chain of custody

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

  1. 1Texakoma E & P, LLCMar 2013 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
751796-99DrillTexakoma E & P, LLCNov 19, 2012Nov 26, 2012Dec 30, 20128,990

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-14-9081————

Formation tops

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

FormationMD ftSubsea
Brown Dolomite3,918-1,314
Kansas City7,654-5,050
Des Moines8,510-5,906

Perforations

Perforated and open-hole intervals.

FromToType
7,6907,696Perforated
7,7427,748Perforated
7,7907,798Perforated
7,8367,842Perforated
7,8647,870Perforated
7,9507,958Perforated
8,5628,568Perforated
8,6608,668Perforated
8,7148,720Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,47512.251,150 S
5.58,9908.75500 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
00Jun 15, 2015Aug 19, 2014Yes

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.

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