WELL · 42-199-32720 · DISTRICT 3

Cruse #2

Y

Hardin County · Batson New field · Producing  · Vertical

Cruse #2 (API 42-199-32720) is a well in Hardin County operated by Rein Pusher Operating LLC, completed January 10, 1996 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued December 18, 1995, permitted to 6,500 ft.

It was permitted by Famcor Oil, Inc and has since transferred to Rein Pusher Operating LLC on the wellbore schedule.

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

Its lease has reported 39K barrels of oil and 11 mcf of gas since January 1996, last reporting in July 2026.

Operator of record

Rein Pusher Operating LLC

Permitted by Famcor Oil, Inc; the EWA schedule now lists a different operator.

Brenham, TX · P-5 Y, filed Jul 4, 2026 · 1 permits on file · (512) 423-0058

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleRein Pusher Operating LLC
Production reportsRein Pusher Operating LLCthrough Apr 2026
Latest permitFamcor Oil, IncDec 18, 1995

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
1
permits on file
Dec 18, 1995
last permit issued
Jan 10, 1996
completed
39K
cumulative oil, bbl
11
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1996 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 10, 1996
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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
Cruse O-3-23148Batson NewRein Pusher Operating LLC139K11Jan 1996 – Jul 2026

Oil, barrels lease total

Last 12 months 587 · prior 12 625(-6%)

050100150202420252026

Chain of custody

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

  1. 1Famcor Oil, Inc.Feb 1996 → Jun 2000
  2. 2Pride Energy CompanyJul 2000 → Sep 2019
  3. 3Rein Pusher Operating LLCOct 2019 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
442936-99DrillFamcor Oil, IncDec 18, 1995Dec 18, 1995Dec 19, 19956,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-23148————

Formation tops

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

FormationMD ftSubsea
Frio4,390-4,301
Yegua4,845-4,756

Perforations

Perforated and open-hole intervals.

FromToType
5,2395,245Perforated
5,2515,255Perforated
5,2615,269Perforated
5,2735,279Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,08712.25525 S
5.56,1007.875325 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 26, 1997Feb 20, 1996Yes
00Feb 12, 1997——

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