WELL · 42-469-33577 · DISTRICT 2
Lemke et al G.U. #1
Victoria County · Colettoville (1900) field · Vertical
Lemke ET AL G.U. #1 (API 42-469-33577) is a plugged well in Victoria County, plugged December 12, 2005, last operated by Edge Petroleum Oper. CO. Inc..
The RRC has issued one drilling permit (amended 3 times), issued April 5, 2001, permitted to 4,400 ft.
Operator of record
Houston, TX · P-5 Inactive, filed Jul 15, 2010 · 433 permits on file · (713) 954-5588
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Edge Petroleum Oper. Co. Inc. |
| Production reports | Edge Petroleum Oper. Co., Inc.through Jun 2005 |
| Latest permit | Edge Petroleum Oper. Co., Inc.Apr 5, 2001 |
- 4,400
- total depth, ft
- 4
- permits on file
- Apr 5, 2001
- last permit issued
- May 1, 2001
- completed
- 0
- cumulative oil, bbl
- 208K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · May 2001 THROUGH Dec 2005
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- May 1, 2001
- Shut in
- —
- Plugged
- Dec 12, 2005
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 →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Lemke, et al G.U. G-2-191802 | Colettoville (1900) | Edge Petroleum Oper. Co., Inc. | 1 | 0 | 208K | May 2001 – Dec 2005 |
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.
- 1Edge Petroleum Oper. Co., Inc.May 2001 → Jun 2005
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 507416-94 | Drill | Edge Petroleum Oper. Co., Inc. | Oct 7, 2002 | Apr 5, 2001 | — | 4,400 |
| 507416-96 | Drill | Edge Petroleum Oper. Co., Inc. | Jun 21, 2001 | Apr 5, 2001 | — | 2,000 |
| 507416-97 | Drill | Edge Petroleum Oper. Co., Inc. | Jun 4, 2001 | Apr 5, 2001 | — | 2,000 |
| 507416-99 | Drill | Edge Petroleum Oper. Co., Inc. | Apr 5, 2001 | Apr 5, 2001 | Apr 13, 2001 | 4,400 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-2-191802 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 1,870 | 1,874 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 473 | 12.25 | 280 S |
| 2.875 | 2,038 | 7.875 | 490 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Jan 21, 2003 | Jun 4, 2001 | Yes |
| 00 | Dec 11, 2002 | — | — |
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.
- Wellbore filings for 42-469-33577 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-469-33577 → scanned completion filings
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/46933577, documented in the API reference.