WELL · 42-481-33820 · DISTRICT 3

Rasmussen #1

Y

Wharton County · Bruce Roy (Yegua) field · Temp Abandoned  · Vertical

Rasmussen #1 (API 42-481-33820) is a well in Wharton County operated by Chp Oil & Gas Company L.C., completed February 15, 1996 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit, issued August 24, 1995, permitted to 8,000 ft.

It was permitted by Ken Petroleum Corporation and has since transferred to Chp Oil & Gas Company L.C. on the wellbore schedule.

Completion filings report 3 formation tops, including Greta, Basis Frio, Jackson.

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

Operator of record

CHP Oil & Gas Company L.C.

Permitted by Ken Petroleum Corporation; the EWA schedule now lists a different operator.

EL Campo, TX · P-5 Y, filed Aug 4, 2025 · 6 permits on file · (979) 543-8698

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCHP Oil & Gas Company L.C.
Production reportsCHP Oil & Gas Company, L.C.through Apr 2025
Latest permitKen Petroleum CorporationAug 24, 1995

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

8,000
total depth, ft
1
permits on file
Aug 24, 1995
last permit issued
Feb 15, 1996
completed
0
cumulative oil, bbl
523K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 1996 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Feb 15, 1996
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Rasmussen G-3-157722Bruce Roy (Yegua)CHP Oil & Gas Company, L.C.10523KFeb 1996 – Jul 2026

Gas, mcf lease total

Last 12 months 0 · prior 12 1,429(-100%)

0200400600202420252026

Chain of custody

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

  1. 1Ken Petroleum CorporationFeb 1996 → Feb 2019
  2. 2CHP Oil & Gas Company, L.C.Mar 2019 → Apr 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
439174-99DrillKen Petroleum CorporationAug 21, 1995Aug 24, 1995Sep 6, 19958,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-157722————

Formation tops

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

FormationMD ftSubsea
Greta3,590-3,574
Basis Frio5,215-5,199
Jackson5,692-5,676

Perforations

Perforated and open-hole intervals.

FromToType
7,6857,718Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.7581014.75555 S
7.6255,8159.8751,350 S
57,8206.75220 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 21, 1996Mar 11, 1996Yes
00May 7, 1996——

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