WELL · 42-325-33965 · DISTRICT 1
Mora #1
Medina County · Bear Creek field · Shut IN · Vertical
Mora #1 (API 42-325-33965) is a well in Medina County operated by Benchmark Texas Petroleum LLC., completed April 16, 2013 and listed as shut in on the RRC schedule.
The RRC has issued one drilling permit, issued March 1, 2013, permitted to 2,500 ft.
It was permitted by Maverick Energy Group, Inc. and has since transferred to Benchmark Texas Petroleum LLC. on the wellbore schedule.
Completion filings report 2 formation tops, including Escondido, Olmos.
No lease production has been reported under this well’s leases.
Operator of record
Benchmark Texas Petroleum LLC.
Permitted by Maverick Energy Group, Inc.; the EWA schedule now lists a different operator.
Tulsa, OK · P-5 Y, filed May 4, 2026 · 49 permits on file · (512) 497-7258
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Benchmark Texas Petroleum LLC. |
| Production reports | none |
| Latest permit | Maverick Energy Group, Inc.Mar 1, 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,500
- total depth, ft
- 1
- permits on file
- Mar 1, 2013
- last permit issued
- Apr 16, 2013
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Apr 2013 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Apr 16, 2013
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Delinquent
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 →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Mora O-1-17557 | Bear Creek | Benchmark Texas Petroleum, LLC. | 1 | 0 | 0 | Apr 2013 – Jul 2026 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 757609-99 | Drill | Maverick Energy Group, Inc. | Feb 27, 2013 | Mar 1, 2013 | Mar 13, 2013 | 2,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-1-17557 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 628 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 1,780 | 2,180 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 4.5 | 2,180 | 6.75 | 357 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Jul 31, 2014 | Oct 4, 2013 | Yes |
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-325-33965 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-325-33965 → scanned completion filings
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/32533965, documented in the API reference.