WELL · 42-201-32977 · DISTRICT 3

Icce #1

Y

Harris County · Hockley field · Shut IN  · Vertical

Icce #1 (API 42-201-32977) is a well in Harris County operated by Kebo Oil & Gas Inc., completed October 30, 2018 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit, issued December 31, 2018, permitted to 2,500 ft.

Completion filings report 9 formation tops, including Miocene (undifferentiated), Caprock, Caproete, Cole - Disposal.

No lease production has been reported under this well’s leases.

Operator of record

Kebo Oil & Gas Inc.

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 scheduleKebo Oil & Gas Inc.
Production reportsnone
Latest permitKebo Oil & Gas, Inc.Dec 31, 2018
2,500
total depth, ft
1
permits on file
Dec 31, 2018
last permit issued
Oct 30, 2018
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2019 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 30, 2018
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

29.965612, -95.828090

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Harris County.

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
Icce O-3-27869HockleyKebo Oil & Gas, Inc.100Apr 2019 – Jul 2026

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

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
845427-99DrillKebo Oil & Gas, Inc.Oct 4, 2018Dec 31, 2018Oct 18, 20182,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-27869————

Formation tops

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

FormationMD ftSubsea
Miocene (undifferentiated)MIOCENE1,762-1,756
CaprockCAPROCK - DISPOSAL——
Caproete——
Cole - Disposal——
Fairbanks - Disposal——
Fleming - Disposal——
FrioFRIO - DISPOSAL——
JacksonJACKSON - DISPOSAL——
Miocene (undifferentiated)MIOCENE - DISPOSAL——
VicksburgVICKSBURG - DISPOSAL——

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,02211224 S
5.52,1137.875505 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
00May 4, 2021Jan 4, 2021Yes

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.

Nearby wells and their tops

NEAREST 2 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well's tops beside its 2 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Warren Ranch42-201-32963

0.5 KM · Texas Oil Resources Oper, LLC · Section with this well →

Miocene (undifferentiated)2,140-1,970
Caprock—
Cole - Disposal—
Cook Mountain—
Fairbanks - Disposal—
Fleming - Disposal—
Frio—
Jackson—

10 TOPS · FIRST 8

Warren Ranch42-201-32639

3.2 KM · Texas Oil Resources Oper, LLC · Section with this well →

Catahoula2,388-2,187
Frio2,550-2,349

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