I have to think with my head & not my heart this time around. Come tomorrow, trading may resume.
Seabee was estimated at 3800ft, but in the last rns, it states it was at 4272 ft. That’s a 472ft difference. Big discrepancy. So the question here is, is the Nanushuk further down?
The last rns, “Intersected a zone of interest in the Nanushuk Formation between 4460’ and 4530’.
In January Presentation
slide 13, depth of N5 is 4520’ to 4570’. N4 depth is 4610’ to 4710’ (I hope I read it correctly)
Question here is, if they reached 4530 ft does that mean they’ve only just entered 10ft of N5 with still 40 ft of N5 to go Or Should I apply 472ft difference as mentioned above and presume they haven’t drilled into N5
The suspicious Twitter Account @Alaskaoilandgas which tweeted Thursday night (our time) “Winx1 - early signs of a commercial discovery drilling deeper” ~ Courtesy of Gliteratti Tweet was deleted and the Account no longer exist.
so question here is, did they stop and halt re ASX rules to report HC or forced to go into TH because of the suspicious tweet and was forced to inform the market with the interim drilling results
01/03/2019 @ 7:27pm RMP tweets “Oil shows have been observed whilst drilling in the Nanushuk in the Winx-1 exploration well!! ”
Question here is, why would RMP tweet it hours after such a badly written rns was received . and with exclamation marks!! ?
Is Bandy up to his old tricks or is he delusional some might say. In my head, RMP is our partner, surely DW would address this tweet to RMP or is it out of DW’s jurisdiction. Or is RMP trying to communicate with us realising the RNS was misread. Very confusing this one
I agree with most that the RNS was written poorly. On a quick scan as I had to rush out the door, my eyes were only focused on water, no oil and lower commercial oil in Nanushuk. Trying to enjoy an event that evening with thoughts Of shite Thats it, we are done - The Nanushuk was the Primary Target. Winx is a duster .. I too would have probably panicked sold if we weren’t on TH. Speaking of that, Was really upset how it all happened. we were on TH, of all days, bloomin Friday. Then London receive the news and trade and watch the SP fall and there’s nothing I could do to save my investment. But now .. half heartedly relieved it happened that way. I was able to read n re-read the rns’s carefully, read posters thoughts and do some calculations of my own. In addition to the possibility of rns Monday morning. Still none the wiser though
02/02/2019 @ 7:52pm Share_Talk on Twitter tweeted “Drilling continues, targeting the Nanushuk 4 and 5 sands” But they have not shared evidence of this statement
Courtesy of JofHoggit LSE 88e Saturday 10:51
clients3.weblink.com.au/pdf/88E/02070754.pdf
Have a look at slide 14. Bitty black line above N5. Can see why it's water logged, any water from above will just be Sat there. Black line above N4 looks solid and thick, hope that's our seal. Updip location so if any water that would be downdip left and right and oil sat nicely at the top where Winx well intersects. Also these stratigraphic traps for brookian plays (nanushuk and torok) are generally pretty flat and the oil gets trapped between different layers of sediment if one of the ancient muddier layers can form a good seal. As is, this upside down bowl shape is good for pooling oil in as it migrates upwards if that does prove to be a good seal the oil can't go any further, can't go up, can't go sideways. We are in for a treat next week, I can feel it.Morning all
Going to give it a rest for now. Doing my head in atm. House to clean and laundry to do. My conclusion for now is, if they haven’t completely drilled into N5 or N4, they would have done so over the weekend. If they hit HC/oil then I would expect a RNS first thing Monday morning re ASX rules. If no RNS Monday then in my mind, no oil was found.
All imho. Just my thoughts. Had to share & release otherwise I’m going to go bonkers for the rest of today and get nothing done. Thanks for listening
I wish you all the very best of luck. Enjoy your Sunday
Expand
(20min delay)
