SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Non-Tech : Any info about Iomega (IOM)?

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Jeffery E. Forrest who wrote (9461)10/20/1996 11:51:00 AM
From: Cogito   of 58324
 
Jeffrey, regarding your predictions -

>>If you will go back and look at my posts, I believe I nailed it quite well. I predicted that the price would remain in a trading range of 21-24 until earnings (IT DID)
I predicted that earnings would be a non-event (IT WAS)<<

On the first one, you were close. Actually, from October 1st through earnings, IOMG closed above 24 twice (including 25.859 on 10/16) and went as high as 26 5/8 on the intraday. Intraday numbers were above 24 on six different days. The price was also below 21 twice on the intraday, but not too far below.

I'm glad I didn't place a limit order to sell at 24 based on your numbers. (Of course, I wouldn't buy or sell based on anyone's numbers other than my own.) I'm just making the point that you were close, but didn't exactly nail it.

As for the second prediction, from the standpoint of numbers alone, you were right. At least so far. And, to give credit where it's due, it was a pretty gutsy call to say the earnings report would not make the price move. Especially with some here predicting a huge rally and short squeeze, and others, notably bull, calling for single digits.

As to your prediction that there will be no short squeeze at any point, we'll see. I don't think anyone can call that one either way just yet. This is a stock given to serious volatility, after all, and we're not on the big board yet.

- Allen
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext