Slawson Exploration Company, a subsidiary of Slawson Companies.
See also NOG. NOG has partnered with Slawson.
Slawson is doing some very interesting things: I have found three occasions on which Slawson has drilled one well just 105 feet or so from another well, in the same section. There are probably many more examples, but I found these three in a matter of minutes. Even EOG doesn't seem to be doing that. EOG puts a well in each section; BEXP is pioneering 24- and 28-stage fractures; most of WLL's wells are 1280-acre spacing; and now, it looks like Slawson is putting two wells right next to each other. Very interesting. I noted this when looking at the "active rigs" and saw Slawson ready to move the rig on Skybolt to Howitzer. December, 2010 (Update: obviously things have changed: EOG now putting three wells in a section. Other producers putting multiple wells on one site/pad -- March 29, 2010)
NEWS
June 21, 2014: NDIC order for the huge Slawson case in Big Bend oil field.
March 29, 2014: a thousand more wells for Slawson in Big Bend oil field?
March 27, 2012: Slawson wells updated.
October 6, 2010: GeoResources reports results of its Slawson wells.
July 4, 2010: Slawson and Voyager partnering in Wyoming's Niobrara. Voyager's CEO is J. R. Reger, of the Billings, MT, Reger family and NOG.
March 30, 2010: Slawson Snake Eyes. Slawson has been granted two permits for another pair of snake eyes, this time in Van Hook oil field: #18870, Moray Federal 1-10H and #18871, Neptune 1-15H, both in NENW 15-151N-92W. In addition, Slawson was granted another permit the same day (today) for another well in the Van Hook field, #18872, Mustang 1-22H, SWSE 22-151N-92W.
March 29, 2010: Slawson Snake Eyes. Slawson has been granted a permit for another well on same pad as earlier well in the Big Bend oil field, continuing a trend I first noted back in December, 2009. I called them "EcoPads Lite," but I think I will start calling them "Slawson Snake Eyes." The new permit, #18854, Silencer 1-29H, joins #18574, Mole 1-20H, on section 20-151-92. One lateral will go north, and one lateral will go south, no doubt.
February 27, 2010: Slawson's string of wells in the Kittleson Slough field.
February 8, 2010: Interview with Slawson CEO.
February 9, 2010: A very nice Slawson well reported Feb 9, 2010 -- 1,208 bopd; 42,000 bbls in first 59 days; Fox 1-28H in the Van Hook field. Thoughts on Slawson; my sentiments exactly.
February 8, 2010: A new partner with Triangle Petroleum, a new player in the Bakken.
Slawson: 48 wells on the confidential list; a most intriguing operator; not publicly traded; see the number of Slawson wells in Big Bend/Van Hook. Are Slawson wells 640-acre spacing still? January 23, 2010.
Slawson: Eco-Pads Lite? Slawson drilling two wells from one pad; one lateral going north; one lateral going south. December 15, 2009.
any information on 18871
ReplyDeleteWhat information are you looking for? The name of the well? Partners? The initial production (IP)? The location? Current production? If you use the search application in the blog site it will take you to 18871.
ReplyDeletepermit 18871 any informaton on the production i think it is off the confidential list
ReplyDeleteI don't subscribe to premium services so I don't know monthly production. The folks over at the Bakken Shale Discussion Group are generally very helpful in providing updated information.
ReplyDeleteIt should be a very good well. My database shows that its IP was 1,394 barrels -- which is a very good well and is located in a very good field, the Van Hook.
I don't subscribe to premium services because I am already inundated with too much data; I cannot keep up with the data I get and I am afraid the NDIC data would simply overwhelm me. I try to balance the big picture with a little data from specific wells.
Bruce,
ReplyDeleteI am having a hard time locating your reminder to an Indiana family you previously referenced. Please advise.
I'll send them an e-mail and link them to this page to see if they have any questions. I found their e-mail which was sent on January 19, 2010.
ReplyDelete