acf/google-ad-placement

Bruce Berkowitz of Fairholme Capital is going to present at the Harbor Investment Conference this week from New York City, and some are speculating that he could announce a potential transaction regarding St. Joe <span class="ticker"
                data-ticker="JOE"
                data-exchange="NYSE"
                style="display: inline-block;">JOE</span> at the conference. 

Personally, I don't think he will announce anything major at the conference, like a full takeover of the company, but perhaps he will lay out his thesis on what he believes the company is worth, similar to what David Einhorn of Greenlight Capital did at the <a href="http://www.benzinga.com/life/hedge-funds/10/10/522527/value-investing-congress-an-overview-of-david-einhorn-joe">Value Investing Congress</a> in October.

Some have <a href="http://www.benzinga.com/trading-ideas/long-ideas/11/01/773971/david-einhorn-is-wrong-joe">said</a> that Einhorn is wrong on this name, despite saying that the company was only worth $7-$10 per share.  Shares are far higher than that today, trading around the $27 level, and are higher than when Einhorn discussed it during his presentation.  Shares of JOE initially spiked down after Einhorn first revealed his short position in St. Joe, but are now above that October level.

Real estate in Florida is starting to recover, slowly but surely, and over time, the company will be worth far more than what Einhorn says it's worth.  That's just the nature of real estate.

Perhaps the company will have to take some writedowns for its land, as per the <a href="http://www.benzinga.com/life/hedge-funds/11/01/769569/the-st-joe-company-dropping-on-sec-concerns-joe">SEC inquiry,</a> but I suspect it won't be nearly as much as Einhorn thinks.  

This has been a battle of the <a href="http://www.benzinga.com/life/hedge-funds/10/10/524020/clash-of-the-titans-joe">industry titans</a> for some time, and investors will be hanging on to see what Berkowitz has to say on Thursday.

Application error: a client-side exception has occurred (see the browser console for more information).