TEXAS · WELLS · WILBARGER COUNTY · API 42-487-82724 · 09 DISTRICT
Fargo Unit #2001
Shut inOil well
- Operator of record
- Burk Royalty Co. Ltd.
- County
- Wilbarger
- Field
- Fargo (Consolidated)
An oil well in Wilbarger County, Texas, operated by Burk Royalty Co. Ltd. RRC status: shut in.
Completed in 2 fields: Fargo (Consolidated), Fargo (Canyon 3900).
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.
Completions
ONE PER FIELD THE WELL IS COMPLETED IN
| Field | Status | Perforations, ft | Completed |
|---|---|---|---|
| Fargo (Consolidated) | Shut in | — | Oct 5, 1979 |
| Fargo (Canyon 3900) | Not on schedule | — | Oct 5, 1979 |
Operators of record
| Operator | From | To |
|---|---|---|
| Burk Royalty Co., Ltd. | May 1, 2023 | today |
| Unitex Oil & Gas, L.L.C. | Jul 1, 2017 | May 1, 2023 |
| Tradition Resources Oper, LLC | Feb 1, 2014 | Jul 1, 2017 |
| Tradition Resources LLC | Sep 1, 2011 | Feb 1, 2014 |
| Vess Oil Corporation | May 1, 2008 | Sep 1, 2011 |
| Apache Corporation | Jul 1, 2000 | May 1, 2008 |
| Collins & Ware, Inc. | Jul 1, 1996 | Jul 1, 2000 |
| Amerada Hess Corporation | May 1, 1988 | Jul 1, 1996 |
Well record
- API number
- 42-487-82724
- Coordinates
- 34.31931, -99.28795 ↗
- Measured depth
- 4,625 ft
- Property
- Fargo Unit
The Railroad Commission's wellbore schedule lists this well, but no drilling permit is on file for it here, so its permits, completion reports, and formation tops are not shown. Texas reports production by lease, not by well: search the leases →
About this data
Railroad Commission of Texas (RRC): the wellbore schedule, which lists every well the Commission tracks with its operator, field, status, and dates. No drilling permit is on file for this API number, so nothing from the permit record is shown. Texas reports production by lease, not by well. Nothing is estimated.
Developers: this page as JSON is GET /v1/data/wells/4248782724, documented in the API reference.