WELL · 42-481-34212 · DISTRICT 3

Rasmussen #5

N

Wharton County · Gimme Putt (Yegua) field  · Vertical

Rasmussen #5 (API 42-481-34212) is a well in Wharton County operated by United Oil & Minerals Inc., completed June 30, 2000.

The RRC has issued 2 drilling permits (amended once) in 2000, permitted to 7,800 ft.

Completion filings report 2 formation tops, including Frio, Vicksburg.

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

Operator of record

United Oil & Minerals Inc.

Austin, TX · P-5 Y, filed Jun 8, 2001 · 464 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleUnited Oil & Minerals Inc.
Production reportsMagnum Producing, LPthrough Dec 2011
Latest permitUnited Oil & Minerals, Inc.Sep 8, 2000

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

7,800
total depth, ft
3
permits on file
Sep 8, 2000
last permit issued
Jun 30, 2000
completed
0
cumulative oil, bbl
412K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2000 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jun 30, 2000
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
Rasmussen G-3-179674Tail Feathers (Yegua)Zone Ridge Operating, LLC10409KAug 2000 – Jul 2026
Rasmussen G-3-179585Gimme Putt (Yegua)United Oil & Minerals, Inc.102.93KJun 2000 – Dec 2000

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. 1United Oil & Minerals, Inc.Jul 2000 → Jan 2001
  2. 2United Oil & Minerals L. P.Feb 2001 → Sep 2001
  3. 3Magnum Producing, LPSep 2005 → Dec 2011

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
499407-99RecompletionUnited Oil & Minerals, Inc.Sep 8, 2000Sep 8, 2000Aug 7, 20007,665
494882-98DrillUnited Oil & Minerals, Inc.Aug 1, 2000May 9, 2000—7,800
494882-99DrillUnited Oil & Minerals, Inc.May 9, 2000May 9, 2000Jun 6, 20007,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-179585————
—— G-3-179674————

Formation tops

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

FormationMD ftSubsea
Frio3,150-3,039
Vicksburg5,050-4,939

Perforations

Perforated and open-hole intervals.

FromToType
7,2727,300Perforated
7,6667,678Perforated
7,6847,688Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6253,09012.251,321 S
4.57,7507.875365 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
00Jan 8, 2001Sep 12, 2000Yes
00Dec 27, 2000Aug 2, 2000Yes
00Nov 29, 2000——
00Nov 27, 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/48134212, documented in the API reference.