WELL · 42-469-32614 · DISTRICT 2

Keeran Ranch #3

Plugged

Victoria County · Emily K. Campbell (5800) field  · Vertical

Keeran Ranch #3 (API 42-469-32614) is a plugged well in Victoria County, plugged May 20, 1998, last operated by Freddy S Well Service Inc..

The RRC has issued one drilling permit (amended once), issued August 3, 1988, permitted to 6,500 ft.

It was permitted by Koba Oil Corp. and has since transferred to Freddy S Well Service Inc. on the wellbore schedule.

Completion filings report 3 formation tops, including Greta, Upper Sinton Sand, Frio.

Its lease has reported 817 barrels of oil and 8 mcf of gas since January 1993, last reporting in March 2025. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Freddy S Well Service Inc.

Permitted by Koba Oil Corp.; the EWA schedule now lists a different operator.

Victoria, TX · P-5 Y, filed Dec 4, 2025 · (361) 652-8779

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleFreddy S Well Service Inc.
Production reportsS.G. Operating Corp.through Nov 1993
Latest permitKoba Oil Corp.Aug 3, 1988

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

6,500
total depth, ft
2
permits on file
Aug 3, 1988
last permit issued
Oct 10, 1988
completed
817
cumulative oil, bbl
8
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Mar 2025

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 10, 1988
Shut in
—
Plugged
May 20, 1998

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; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Keeran Ranch O-2-4881Emily K. Campbell (5800)Freddy's Well Service, Inc.28178Jan 1993 – Mar 2025

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. 1S.G. Operating Corp.Mar 1993 → Nov 1993

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
349552-98DrillKoba Oil Corp.Nov 28, 1988Aug 3, 1988—6,452
349552-99DrillKoba Oil Corp.Jul 29, 1988Aug 3, 1988—6,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-2-4881————

Formation tops

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

FormationMD ftSubsea
GretaGRETA SAND4,980-4,936
Upper Sinton Sand5,540-5,496
FrioFRIO SAND "5800"5,790-5,746

Perforations

Perforated and open-hole intervals.

FromToType
5,8125,815Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62566712.25220 S
4.56,2637.875745 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
00Feb 22, 1989Dec 27, 1988Yes
00Jan 7, 1989——

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