WELL · 42-445-32137 · DISTRICT 8

Pusey 39 #2

Y

Terry County · Tokio (Leonard) field · Producing  · Vertical

Pusey 39 #2 (API 42-445-32137) is a well in Terry County operated by Rein Pusher Operating LLC, completed September 21, 2007 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued July 17, 2006, permitted to 9,000 ft.

It was permitted by Nearburg Producing Company and has since transferred to Rein Pusher Operating LLC on the wellbore schedule.

Its lease has reported 75.6K barrels of oil since March 2006, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Rein Pusher Operating LLC

Permitted by Nearburg Producing Company; 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 permitNearburg Producing CompanyJul 17, 2006

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

9,000
total depth, ft
2
permits on file
Jul 17, 2006
last permit issued
Sep 21, 2007
completed
75.6K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2006 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Sep 21, 2007
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; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Pusey 39 O-11-68998Tokio (Leonard)Rein Pusher Operating LLC275.6K0Mar 2006 – Jul 2026

Oil, barrels lease total

Last 12 months 1,750 · prior 12 1,924(-9%)

0100200300202420252026

Chain of custody

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

  1. 1Nearburg Producing CompanyMar 2006 → Sep 2017
  2. 2Three Forks Resources, LLCOct 2017 → May 2019
  3. 3Rein Pusher Operating LLCJun 2019 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
622701-98DrillNearburg Producing CompanyOct 12, 2009Jul 17, 2006Jul 9, 20079,000
622701-99DrillNearburg Producing CompanyJul 17, 2006Jul 17, 2006Jul 9, 20079,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-11-68998————

Perforations

Perforated and open-hole intervals.

FromToType
8,5708,590Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6252,42812.251,115 S
5.58,8547.8752,495 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
00Jun 2, 2010Feb 4, 2008Yes
00Aug 5, 2009——

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