TEXAS · WELLS · LOVING COUNTY · API 42-301-31843 · DISTRICT 7B
Excelsior 12 (Allocation) #1H
Loving County · Sandbar (Bone Spring) field · Horizontal
Excelsior 12 (Allocation) #1H (API 42-301-31843) is a plugged horizontal well in Loving County, plugged November 1, 2024, last operated by Eog Resources Inc..
The RRC has issued one drilling permit (amended once), issued September 13, 2012, permitted to 10,000 ft.
Completion filings report 3 formation tops, including Cherry Canyon, Brushy Canyon, Bone Spring.
Its 2 leases have reported 293K barrels of oil and 1.66M mcf of gas since February 2013, with no volume in the three years through August 2026. The leases carry 2 wells, so these are lease totals, not this well alone.
Operator of record
- Based in
- Midland, TX
- P-5 status
- Active – Extension (X)
- P-5 last filed
- Aug 12, 2026
- Permits on file
- 16,354
- Phone
- (713) 651-7000
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | EOG Resources Inc. |
| Production reports | EOG Resources, Inc.through May 2022 |
| Latest permit | EOG Resources, Inc.Sep 13, 2012 |
- 10,000
- total depth, ft
- 2
- permits on file
- Sep 13, 2012
- last permit issued
- Mar 19, 2013
- completed
- 293K
- cumulative oil, bbl
- 1.66M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · FEB 2013 THROUGH MAY 2022
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Mar 19, 2013
- Shut in
- —
- Plugged
- Nov 1, 2024
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.
Wells nearby
Every well with a location on file around this well, in any state, nearest first.
Texas locations come from drilling permits, so most older Texas wells have none and are not listed.
Lease production
PDQ LEASE REPORTS · REPORTED THROUGH AUG 2026
Texas reports oil by lease, not by well. These are the 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Excelsior 12 (Allocation) G-10-285239 | Sandbar (Bone Spring) | EOG Resources, Inc. | 1 | 291K | 1.66M | Feb 2013 – May 2022 |
| Excelsior 12 (Allocation) O-10-45799 | Sandbar (Bone Spring) | EOG Resources, Inc. | 1 | 1.99K | 0 | Feb 2013 – Feb 2013 |
No volumes reported on these leases in the last three years.
Wells named Excelsior 12 (Allocation)
EOG Resources Inc.'s other wells filed under this lease name in Loving County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.
Loading the lease's wellsChain of custody
Every operator that reported production on this well's lease, in order.
- 1EOG Resources, Inc.Feb 2013 → Nov 2021
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 747552-98 | Drill | EOG Resources, Inc. | Apr 4, 2013 | Sep 13, 2012 | Oct 25, 2012 | 10,000 |
| 747552-99 | Drill | EOG Resources, Inc. | Sep 4, 2012 | Sep 13, 2012 | Oct 25, 2012 | 10,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Mar 19, 2013 | Excelsior 12 (Allocation) G-10-285239 | Sandbar (Bone Spring) | EOG Resources Inc. | Plugged | — |
| Mar 19, 2013 | Excelsior 12 (Allocation) O-10-45799 | Sandbar (Bone Spring) | EOG Resources Inc. | Plugged | — |
Formation tops
As filed on W-2/G-1. Subsea from 3,064 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Cherry Canyon | 5,745 | -2,681 |
| Brushy Canyon | 7,252 | -4,188 |
| Bone Spring | 8,805 | -5,741 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 9,690 | 14,256 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 905 | 17.5 | 650 S |
| 9.625 | 4,607 | 12.25 | 1,200 S |
| 5.5 | 14,286 | 8.75 | 2,025 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Dec 11, 2018 | Sep 18, 2018 | — |
| 00 | Feb 26, 2015 | Apr 17, 2013 | Yes |
Well logs
1 log loaded from the RRC's log index, the latest received Dec 7, 2015. Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.
Open the RRC's log search for this well ↗| Logas described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| RESISTIVITY | TIFF | 0 to 5,012 | Dec 7, 2015run Jan 16, 2013 | 2.38 |
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.
- Wellbore filings for 42-301-31843 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-301-31843 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search for it. The University Lands library has no per-well link: then paste it into its 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/30131843, documented in the API reference.