WELL · 42-323-32531 · DISTRICT 1

Alkek #2233

Plugged

Maverick County · Chittim (Eagleford) field  · Vertical

Alkek #2233 (API 42-323-32531) is a plugged well in Maverick County, plugged October 20, 2010, last operated by Txco Resources Inc..

The RRC has issued one drilling permit (amended once), issued March 8, 1999, permitted to 6,250 ft.

It was permitted by Exploration Company, The and has since transferred to Txco Resources Inc. on the wellbore schedule.

Completion filings report 4 formation tops, including Austin Chalk, Eagle Ford, Georgetown, Glen Rose.

Its lease has reported 110 barrels of oil and 5 mcf of gas since December 1999, last reporting in February 2011.

Operator of record

Txco Resources Inc.

Permitted by Exploration Company, The; the EWA schedule now lists a different operator.

San Antonio, TX · P-5 Y, filed Sep 3, 2010 · 201 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleTxco Resources Inc.
Production reportsTxco Resources Inc.through Jun 2008
Latest permitExploration Company, TheMar 8, 1999

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

6,250
total depth, ft
2
permits on file
Mar 8, 1999
last permit issued
Dec 9, 1999
completed
110
cumulative oil, bbl
5
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 1999 THROUGH Feb 2011

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 9, 1999
Shut in
—
Plugged
Oct 20, 2010

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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Alkek O-1-14285Chittim (Eagleford)Txco Resources Inc.11105Dec 1999 – Feb 2011

No volumes reported on these leases in the last three years.

Chain of custody

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

  1. 1Exploration Company, TheDec 1999 → Sep 2004
  2. 2Txco Resources Inc.Jun 2008 → Jun 2008

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
483132-98DrillExploration Company, TheDec 13, 1999Mar 8, 1999—6,250
483132-99DrillExploration Company, TheMar 8, 1999Mar 8, 1999Mar 9, 19996,250

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-14285————

Formation tops

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

FormationMD ftSubsea
Austin Chalk1,190-319
Eagle FordEAGLEFORD2,210-1,339
Georgetown3,168-2,297
Glen Rose4,480-3,609

Perforations

Perforated and open-hole intervals.

FromToType
2,6102,687Perforated
2,7142,748Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62535012.25255 S
4.56,1977.875425 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
00Mar 24, 2000Dec 13, 1999Yes
00Mar 10, 2000——

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