WELL · 42-025-32188 · DISTRICT 2
Younts #1
Bee County · Vertical
Younts #1 (API 42-025-32188) is a plugged well in Bee County, plugged September 7, 2000, last operated by Kebo Oil & Gas, Inc..
The RRC has issued 3 drilling permits between 1984 and 1997, permitted to 18,000 ft.
Completion filings report 4 formation tops, including Recklaw, Slick, Luling, 1st Massive.
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 | none |
| Production reports | none |
| Latest permit | Kebo Oil & Gas, Inc.Aug 29, 1997 |
- 18,000
- total depth, ft
- 3
- permits on file
- Aug 29, 1997
- last permit issued
- —
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jan 1993
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- Sep 7, 2000
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 |
|---|---|---|---|---|---|---|
| Meyer, Z.Y. G-2-130899 | Rollem (1ST. Massive) | Arco Oil & Gas Co. | 1 | 0 | 0 | Jan 1993 – Jan 1993 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 466915-99 | Reenter | Kebo Oil & Gas, Inc. | Aug 29, 1997 | Aug 29, 1997 | — | 10,500 |
| 357616-99 | Recompletion | Arco Oil & Gas Co. | Mar 31, 1989 | Apr 3, 1989 | — | 12,438 |
| 249888-99 | Drill | Arco Oil & Gas Co. | Aug 28, 1984 | Aug 29, 1984 | Sep 6, 1984 | 18,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-2-130899 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 260 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Recklaw | 9,288 | -9,028 |
| Slick | 9,735 | -9,475 |
| Luling | 10,110 | -9,850 |
| 1ST Massive | 10,496 | -10,236 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 10,500 | 10,534 | Perforated |
| 12,078 | 12,095 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 16 | 2,986 | 20 | 2,400 S |
| 11.75 | 9,948 | 14.75 | 2,400 S |
| 7.625 | 10,280 | 8.5 | 410 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 | Jun 16, 1989 | Apr 25, 1989 | Yes |
| 00 | Jun 15, 1989 | — | — |
| 00 | Jun 12, 1985 | May 1, 1985 | — |
| 00 | May 14, 1985 | — | — |
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-025-32188 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-025-32188 → 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/02532188, documented in the API reference.