WELL · 42-025-32895 · DISTRICT 2

May #3

N

Bee County · May Ranch (Hockley) field  · Vertical

May #3 (API 42-025-32895) is a well in Bee County operated by Apex Energy Inc., completed June 11, 1998.

The RRC has issued one drilling permit, issued May 26, 1998, permitted to 4,150 ft.

It was permitted by Legacy Oil & Gas, Inc. and has since transferred to Apex Energy Inc. on the wellbore schedule.

Completion filings report one formation top, including Hockley.

Its 2 leases have reported 74.9K barrels of oil and 24.7K mcf of gas since June 1998, last reporting in July 2026. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Apex Energy Inc.

Permitted by Legacy Oil & Gas, Inc.; the EWA schedule now lists a different operator.

Corpus Christ, TX · P-5 Y, filed Nov 4, 2025 · 6 permits on file · (361) 815-6366

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleApex Energy Inc.
Production reportsDouble Play Oil & Gas, Incthrough Mar 2014
Latest permitLegacy Oil & Gas, Inc.May 26, 1998

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

4,150
total depth, ft
1
permits on file
May 26, 1998
last permit issued
Jun 11, 1998
completed
74.9K
cumulative oil, bbl
24.7K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 1998 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jun 11, 1998
Shut in
—
Plugged
—

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
May O-2-8523May Ranch (Hockley)Apex Energy, Inc.174.9K11.2KSep 1999 – Jul 2026
May G-2-175396May Ranch (Hockley)Apex Energy, Inc.1013.4KJun 1998 – Feb 2005

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. 1Apex Energy, Inc.Aug 1998 → Dec 2001
  2. 2Double Play Oil & Gas, IncJan 2002 → Mar 2014

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
476601-99DrillLegacy Oil & Gas, Inc.May 26, 1998May 26, 1998May 27, 19984,150

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-2-175396————
—— O-2-8523————

Formation tops

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

FormationMD ftSubsea
Hockley3,800-3,433
Hockley3,900-3,533

Perforations

Perforated and open-hole intervals.

FromToType
3,9053,910Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62551412.25—
4.54,1077.875480 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 2, 2000Oct 6, 1999—
00Apr 13, 2000——
00Mar 30, 2000Mar 29, 1999Yes
00Jan 26, 2000——

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