WELL · 42-253-35327 · DISTRICT 7

Reves #1

Y

Jones County · Jones County Regular field · NO Production  · Vertical

Reves #1 (API 42-253-35327) is a well in Jones County operated by Pure O & G LLC, completed September 17, 2013 and listed as no production on the RRC schedule.

The RRC has issued one drilling permit, issued April 16, 2013, permitted to 2,999 ft.

It was permitted by Royal Texan Energy CO. and has since transferred to Pure O & G LLC on the wellbore schedule.

Completion filings report one formation top, including Swastika.

Its lease has reported 19.2K barrels of oil since September 2013, last reporting in July 2026. The lease carries 3 wells, so these are lease totals, not this well alone.

Operator of record

Pure O & G LLC

Permitted by Royal Texan Energy Co.; the EWA schedule now lists a different operator.

Stamford, TX · P-5 Y, filed Dec 18, 2025 · (325) 669-9877

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePure O & G LLC
Production reportsIcs Energy LLCthrough Apr 2026
Latest permitRoyal Texan Energy Co.Apr 16, 2013

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

2,999
total depth, ft
1
permits on file
Apr 16, 2013
last permit issued
Sep 17, 2013
completed
19.2K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2013 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Sep 17, 2013
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 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Reves O-8-31293Jones County RegularIcs Energy LLC319.2K0Sep 2013 – Jul 2026

Oil, barrels lease total

Last 12 months 153 · prior 12 356(-57%)

0100200202420252026

Chain of custody

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

  1. 1Royal Texan Energy Co.Sep 2013 → Sep 2013
  2. 2Royal Texan Resources Co.Oct 2013 → Nov 2017
  3. 3Orland Oil & Gas LLCDec 2017 → Jun 2024
  4. 4Ics Energy LLCJul 2024 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
760650-99DrillRoyal Texan Energy Co.Apr 12, 2013Apr 16, 2013Jul 8, 20132,999

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-31293————

Formation tops

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

FormationMD ftSubsea
Swastika2,045-495

Perforations

Perforated and open-hole intervals.

FromToType
2,0452,049Open hole

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62512612.2580 S
4.52,0457.875370 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
00Sep 26, 2013Sep 25, 2013Yes

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