TEXAS · WELLS · GAINES COUNTY · AURELIUS LEASE · API 42-165-38500 · DISTRICT 7B

Aurelius #1H

Y

Gaines County · Block a-34 (San Andres) field · Producing  · Horizontal

Aurelius #1H (API 42-165-38500) is a horizontal well in Gaines County operated by Ring Energy Inc., completed May 20, 2017 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued March 2, 2017, permitted to 4,721 ft.

Completion filings report 10 formation tops, including Yates, Queen, Seven Rivers, San Andres.

Its lease has reported 101K barrels of oil and 14.1K mcf of gas since May 2017, last reporting in July 2026.

Operator of record

Ring Energy Inc.

Based in
Midland, TX
P-5 status
Active (A)
P-5 last filed
Feb 9, 2026
Permits on file
997
Phone
(432) 682-7464

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleRing Energy Inc.
Production reportsRing Energy, Inc.through Apr 2026
Latest permitRing Energy, Inc.Mar 2, 2017
4,721
total depth, ft
1
permits on file
Mar 2, 2017
last permit issued
May 20, 2017
completed
101K
cumulative oil, bbl
14.1K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2017 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 20, 2017
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

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
Aurelius O-10-48881Block a-34 (San Andres)Ring Energy, Inc.1101K14.1KMay 2017 – Jul 2026

Oil, barrels lease total

Last 12 months 2,638 · prior 12 4,051(-35%)

05001K202420252026

Gas, mcf lease total

Last 12 months 5,673 · prior 12 3,428(+65%)

05001K202420252026

Chain of custody

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

  1. 1Ring Energy, Inc.May 2017 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
821901-99DrillRing Energy, Inc.Jan 9, 2017Mar 2, 2017Mar 16, 20174,900

Completions

CompletedLeaseFieldOperatorStatusDepth
May 20, 2017Aurelius O-10-48881Block a-34 (San Andres)Ring Energy Inc.Producing4,721

Formation tops

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

FormationMD ftSubsea
YatesYATES - OVERPRESSURE, INERT GAS2,923319
Queen3,054188
Seven Rivers3,054188
San AndresSAN ANDRES - ACTIVE CO2 FLOOD4,667-1,425
Clear ForkCLEARFORK——
Glorieta——
Leonard——
San Angelo——
Spraberry——
Wichita-AlbanyWICHITA ALBANY——

Perforations

Perforated and open-hole intervals.

FromToType
5,0439,680Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,76512.25850 S
5.59,7988.751,952 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 27, 2017Aug 16, 2017Yes

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) and the University Lands library. 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/16538500, documented in the API reference.