WELL · 42-123-33849 · DISTRICT 2
County Line #1
DE Witt County · Wildcat field · Vertical
County Line #1 (API 42-123-33849) is a plugged well in De Witt County, plugged April 8, 2016, last operated by Kebo Oil & Gas Inc..
The RRC has issued one drilling permit (amended once), issued October 24, 2014, permitted to 4,300 ft.
Completion filings report 9 formation tops, including Vicksburg, Pettus, Yegua, Austin Chalk.
Operator of record
Portland, TX · P-5 Y, filed May 4, 2026 · 537 permits on file · (210) 218-1781
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Kebo Oil & Gas Inc. |
| Production reports | none |
| Latest permit | Kebo Oil & Gas, Inc.Oct 24, 2014 |
- 4,300
- total depth, ft
- 2
- permits on file
- Oct 24, 2014
- last permit issued
- Aug 5, 2015
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Aug 2015 THROUGH Apr 2016
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Aug 5, 2015
- Shut in
- —
- Plugged
- Apr 8, 2016
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 |
|---|---|---|---|---|---|---|
| County Line G-2-279963 | Wildcat | Kebo Oil & Gas, Inc. | 1 | 0 | 0 | Aug 2015 – Apr 2016 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 798990-98 | Drill | Kebo Oil & Gas, Inc. | Apr 27, 2015 | Oct 24, 2014 | Jul 17, 2015 | 4,300 |
| 798990-99 | Drill | Kebo Oil & Gas, Inc. | Oct 24, 2014 | Oct 24, 2014 | Jul 17, 2015 | 4,300 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-2-279963 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 295 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Vicksburg | 3,468 | -3,173 |
| Pettus | 3,893 | -3,598 |
| Yegua | 3,984 | -3,689 |
| Austin Chalk | — | — |
| Catahoula | — | — |
| Eagle Ford | — | — |
| EdwardsEDWARDS - H2S | — | — |
| Frio | — | — |
| Wilcox | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 3,893 | 3,896 | Perforated |
| 3,984 | 3,987 | Perforated |
| 4,030 | 4,033 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 1,407 | 12.25 | 560 S |
| 2.875 | 4,303 | 7.875 | 848 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 | May 25, 2016 | Oct 7, 2015 | Yes |
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-123-33849 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-123-33849 → 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/12333849, documented in the API reference.