TEXAS · WELLS · KLEBERG COUNTY · API 42-273-31827 · DISTRICT 04

King Ranch Borregos #605

Plugged

Kleberg County · Borregos (Consolidated Gas) field  · Vertical

King Ranch Borregos #605 (API 42-273-31827) is a plugged well in Kleberg County, plugged February 1, 2010, last operated by Exxon Mobil Corporation.

The RRC has issued 6 drilling permits (amended twice) between 1983 and 1995, permitted to 7,950 ft.

It was permitted by Exxon Corp. and has since transferred to Exxon Mobil Corporation on the wellbore schedule.

Its 4 leases have reported 551K barrels of oil and 3.53M mcf of gas since January 1993, last reporting volume in February 2024. The leases carry 199 wells, so these are lease totals, not this well alone.

Operator of record

Exxon Mobil Corporation

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

Based in
Spring, TX
P-5 status
Active (A)
P-5 last filed
Jul 15, 2026
Permits on file
1,223
Phone
(346) 474-9142

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleExxon Mobil Corporation
Production reportsEOG Resources, Inc.through Feb 2024
Latest permitExxon Corp.Jul 10, 1995

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

7,950
total depth, ft
8
permits on file
Jul 10, 1995
last permit issued
Mar 21, 2005
completed
551K
cumulative oil, bbl
3.53M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Feb 2024

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 21, 2005
Shut in
—
Plugged
Feb 1, 2010

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 4 leases this well is completed on; they carry 199 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Borregos, K. R. & Seeligson O-4-6544Borregos (Combined Zones)EOG Resources, Inc.197550K3.47MJan 1993 – Feb 2024
King Ranch Borregos G-4-149549Borregos (Consolidated Gas)Exxon Mobil Corporation132364.4KDec 1993 – Apr 2005
King Ranch Borregos G-4-112287Borregos (Zone 6687)Exxon Corp.100Jan 1993 – —
— G-4-131068——000—

Oil, barrels lease total

Last 12 months 0 · prior 12 0

02K4K6K202420252026

Gas, mcf lease total

Last 12 months 0 · prior 12 0

05K10K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Exxon Corp.Jan 1993 → Mar 2000
  2. 2Exxon Mobil CorporationApr 2000 → Apr 2005
  3. 3EOG Resources, Inc.Apr 2013 → Feb 2024

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
437642-99RecompletionExxon Corp.Jul 10, 1995Jul 10, 1995—6,940
418168-99RecompletionExxon Corp.Nov 12, 1993Nov 12, 1993Dec 22, 19936,228
395062-99RecompletionExxon Corp.Dec 13, 1991Dec 20, 1991Nov 30, 19927,495
341390-97RecompletionExxon Corp.Sep 20, 1990Jan 15, 1988—7,495
341390-98RecompletionExxon Corp.May 6, 1988Jan 15, 1988—7,495
341390-99RecompletionExxon Corp.Jan 14, 1988Jan 15, 1988—7,495
301098-99RecompletionExxon Corp.Apr 15, 1986Apr 16, 1986—7,950
221713-99DrillExxon Corp.Nov 22, 1983Nov 28, 1983Mar 29, 19847,950

Completions

CompletedLeaseFieldOperatorStatusDepth
Mar 21, 2005King Ranch Borregos G-4-149549Borregos (Consolidated Gas)Exxon Mobil CorporationPlugged—
Dec 1, 1992Borregos K. R. & Seeligson O-4-6544Borregos (Combined Zones)EOG Resources Inc.Plugged—
May 11, 1989King Ranch Borregos G-4-131068Borregos (Zone N-15)Exxon Corp.Plugged—
May 18, 1986King Ranch Borregos G-4-111926Borregos (R-13 SW-2)Exxon Corp.Plugged—
May 18, 1986King Ranch Borregos G-4-111926Borregos (R-13 SW-2)Exxon Corp.Plugged—
May 7, 1984King Ranch Borregos G-4-112287Borregos (Zone 6687)Exxon Corp.Plugged—

Perforations

Perforated and open-hole intervals.

FromToType
4,9184,936Perforated
4,9184,938Perforated
5,1375,162Perforated
5,3215,334Perforated
5,4305,439Perforated
5,8745,880Perforated
6,1706,178Perforated
6,2886,295Perforated
6,6666,676Perforated
6,6876,700Perforated
6,9446,957Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,51612.25710 sx
8.6251,52912.25710 S
8.751,53012.25710 S
8.6251,53012.25710 S
2.8757,474——
2.8757,4837.8751,611 S
8.62515,29712.25710 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Aug 24, 2005Apr 20, 2005—
00Aug 19, 2005Apr 12, 2005—
00Dec 18, 2001Nov 20, 2001—
00Nov 19, 1997Oct 24, 1997—
00Oct 21, 1997Sep 24, 1997Yes
00Apr 10, 1996Sep 24, 1997—
00Jul 18, 1994May 13, 1994Yes
00Jun 13, 1994——
00Mar 25, 1993Feb 9, 1993Yes
00Mar 8, 1993——
00Jan 31, 1990May 30, 1989Yes
00Jul 6, 1989——
00May 24, 1988Oct 13, 1987Yes
00Sep 28, 1984Aug 6, 1984—
00Sep 19, 1984Aug 6, 1984—
00Aug 22, 1984Jul 9, 1984—
00Aug 16, 1984Jul 9, 1984—

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 filed since 2004 open from the RRC's log search for this well; none are loaded here for it.

Find logs withinmiles of this well:List →Map →

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