WELL · 42-423-32314 · DISTRICT 6
Rowley #1
Smith County · Starville East (Travis Peak) field · Producing · Vertical
Rowley #1 (API 42-423-32314) is a well in Smith County operated by Jamex Inc., completed July 2, 2012 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued May 14, 2012, permitted to 9,500 ft.
Completion filings report 3 formation tops, including Massive Anyhydrite, Rodessa, Travis Peak.
Its lease has reported 37.6K barrels of oil since July 2012, last reporting in July 2026.
Operator of record
Lewisville, TX · P-5 Y, filed Apr 4, 2026 · 331 permits on file · (800) 880-1552
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Jamex Inc. |
| Production reports | Jamex, Inc.through Apr 2026 |
| Latest permit | Jamex, Inc.May 14, 2012 |
- 9,500
- total depth, ft
- 1
- permits on file
- May 14, 2012
- last permit issued
- Jul 2, 2012
- completed
- 37.6K
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jul 2012 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Jul 2, 2012
- 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; this well is the only one on it.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Rowley O-6-15120 | Starville, East (Travis Peak) | Jamex, Inc. | 1 | 37.6K | 0 | Jul 2012 – Jul 2026 |
Oil, barrels lease total
Last 12 months 1,425 · prior 12 1,593(-11%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Jamex, Inc.Jul 2012 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 739725-99 | Drill | Jamex, Inc. | May 1, 2012 | May 14, 2012 | May 19, 2012 | 9,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-6-15120 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 440 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Massive Anyhydrite | 7,390 | -6,950 |
| Rodessa | 7,830 | -7,390 |
| Travis Peak | 8,508 | -8,068 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 8,592 | 8,602 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 1,470 | 12.25 | 660 S |
| 5.5 | 8,951 | 8.75 | 1,440 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 | Oct 19, 2012 | Aug 1, 2012 | 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-423-32314 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-423-32314 → 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/42332314, documented in the API reference.