WELL · 42-097-02402 · DISTRICT 9
Walnut Bend Field Unit #1913
Cooke County · Walnut Bend (Consolidated) field · Producing · Vertical
Walnut Bend Field Unit #1913 (API 42-097-02402) is a well in Cooke County operated by Sydri Operating LLC, completed July 24, 2001 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued July 3, 2001, permitted to 5,480 ft.
It was permitted by Gruy Petroleum Management CO. and has since transferred to Sydri Operating LLC on the wellbore schedule.
Completion filings report 3 formation tops, including Cox, Hudspeth, Oil Creek.
Its 2 leases have reported 6.7M barrels of oil and 1.39M mcf of gas since January 1993, last reporting in July 2026. The leases carry 374 wells, so these are lease totals, not this well alone.
Operator of record
Permitted by Gruy Petroleum Management Co.; the EWA schedule now lists a different operator.
- Based in
- Dallas, TX
- P-5 status
- Active (A)
- P-5 last filed
- Mar 11, 2026
- Permits on file
- 46
- Phone
- (214) 373-8626
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Sydri Operating LLC |
| Production reports | Sydri Operating, LLCthrough Apr 2026 |
| Latest permit | Gruy Petroleum Management Co.Jul 3, 2001 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 5,480
- total depth, ft
- 1
- permits on file
- Jul 3, 2001
- last permit issued
- Jul 24, 2001
- completed
- 6.7M
- cumulative oil, bbl
- 1.39M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Jul 24, 2001
- 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 2 leases this well is completed on; they carry 374 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Ramsey, G. L. O-13-2509 | Walnut Bend (Oil Creek Sand) | Sydri Operating, LLC | 4 | 13.9K | 6.15K | Jan 1993 – Jul 2026 |
| Walnut Bend Field Unit O-13-27427 | Walnut Bend (Consolidated) | Sydri Operating, LLC | 370 | 6.69M | 1.38M | Jan 1993 – Jul 2026 |
Oil, barrels lease total
Last 12 months 75,510 · prior 12 90,992(-17%)
Gas, mcf lease total
Last 12 months 21,434 · prior 12 22,769(-6%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Arco Oil & Gas Co.Jan 1993 → Feb 1994
- 2Vastar Resources, Inc.Mar 1994 → May 1999
- 3Gruy Petroleum Management Co.Jun 1999 → Apr 2006
- 4Cimarex Energy Co. of ColoradoMay 2006 → Dec 2012
- 5Merit Energy CompanyJan 2013 → Nov 2020
- 6Team Operating, L.L.C.Dec 2020 → Jun 2021
- 7Sydri Operating, LLCJul 2021 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 511016-99 | Recompletion | Gruy Petroleum Management Co. | Jul 3, 2001 | Jul 3, 2001 | Jul 19, 2001 | 4,650 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Jul 24, 2001 | Walnut Bend Field Unit O-13-27427 | Walnut Bend (Consolidated) | Sydri Operating LLC | Producing | 5,480 |
| Jan 25, 1977 | Ramsey G. L. O-13-2509 | Walnut Bend (Oil Creek Sand) | Sydri Operating LLC | Not on Schedule | — |
| — | Walnut Bend Field Unit No. 2 O-13-13264 | Walnut Bend (Regular) | Arco Oil & Gas Co. | Not on Schedule | — |
Formation tops
As filed on W-2/G-1. Subsea from 808 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Cox | 3,074 | -2,266 |
| Hudspeth | 4,227 | -3,419 |
| Oil Creek | 5,422 | -4,614 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 4,418 | 4,434 | Perforated |
| — | 5,432 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 1,119 | 12 | 350 S |
| 8.625 | 1,119 | — | 350 S |
| 5.5 | 4,849 | 7.875 | 300 S |
| 5.5 | 4,849 | — | 300 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 | Apr 29, 2002 | Jan 8, 2002 | Yes |
| 00 | Mar 12, 2002 | — | — |
| 00 | Jan 12, 1984 | Feb 23, 1977 | — |
| 00 | Jan 12, 1984 | — | — |
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-097-02402 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-097-02402 → 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.
Beyond the permit record
RRC UIC permits · H-10 reported volumes
Injection
- 0
- bbl, last 12 reported months
- 0
- bbl, all reported
- Oct 1993
- reported through
| UIC | Kind | Status | Permitted bbl/d | Max psi | Zone ft |
|---|---|---|---|---|---|
| 000071779 | H-1 Injection | Canceled Nov 9, 1994 | 1,200 | 1,800 | 4,849–4,864 |
MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS
Last 12 months 0 · prior 12 0
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/09702402, documented in the API reference.