WELL · 42-503-42012 · DISTRICT 9
Calvin Lease #5S
Young County · Young County Regular field · Vertical
Calvin Lease #5S (API 42-503-42012) is a plugged well in Young County, plugged October 18, 2023, last operated by Bmf Oilfield Services LLC.
The RRC has issued one drilling permit, issued September 18, 2012, permitted to 1,000 ft.
It was permitted by Rog Enterprises, Inc. and has since transferred to Bmf Oilfield Services LLC on the wellbore schedule.
Its lease has reported 735 barrels of oil since December 2012, last reporting in July 2026. The lease carries 8 wells, so these are lease totals, not this well alone.
Operator of record
Permitted by Rog Enterprises, Inc.; the EWA schedule now lists a different operator.
Wichita Falls, TX · P-5 Y, filed Sep 8, 2023 · (432) 290-0587
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | BMF Oilfield Services LLC |
| Production reports | Rog Enterprises, LLCthrough Aug 2019 |
| Latest permit | Rog Enterprises, Inc.Sep 18, 2012 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 1,000
- total depth, ft
- 1
- permits on file
- Sep 18, 2012
- last permit issued
- Dec 16, 2012
- completed
- 735
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Dec 2012 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Dec 16, 2012
- Shut in
- —
- Plugged
- Oct 18, 2023
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 8 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Calvin Lease O-13-32573 | Young County Regular | BMF Oilfield Services LLC | 8 | 735 | 0 | Dec 2012 – Jul 2026 |
No volumes reported on these leases in the last three years.
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Rog Enterprises, Inc.Sep 2013 → May 2014
- 2Rog Enterprises, LLCJun 2014 → Aug 2019
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 747524-99 | Drill | Rog Enterprises, Inc. | Sep 3, 2012 | Sep 18, 2012 | Dec 16, 2012 | 1,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-13-32573 | — | — | — | — |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 4.5 | 825 | 7.875 | 230 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 | Aug 26, 2014 | Jun 11, 2014 | 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-503-42012 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-503-42012 → 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/50342012, documented in the API reference.