Shareholders of Systemax, Inc. (Symbol: SYX) looking to boost their income beyond the stock's 2.2% annualized dividend yield can sell the September covered call at the $22.50 strike and collect the premium based on the $2.10 bid, which annualizes to an additional 23.6% rate of return against the current stock price (at Stock Options Channel we call this the YieldBoost), for a total of 25.8% annualized rate in the scenario where the stock is not called away. Any upside above $22.50 would be lost if the stock rises there and is called away, but SYX shares would have to advance 2.5% from current levels for that to happen, meaning that in the scenario where the stock is called, the shareholder has earned a 12.1% return from this trading level, in addition to any dividends collected before the stock was called.
In general, dividend amounts are not always predictable and tend to follow the ups and downs of profitability at each company. In the case of Systemax, Inc., looking at the dividend history chart for SYX below can help in judging whether the most recent dividend is likely to continue, and in turn whether it is a reasonable expectation to expect a 2.2% annualized dividend yield.
Below is a chart showing SYX's trailing twelve month trading history, with the $22.50 strike highlighted in red:
The chart above, and the stock's historical volatility, can be a helpful guide in combination with fundamental analysis to judge whether selling the September covered call at the $22.50 strike gives good reward for the risk of having given away the upside beyond $22.50. (Do most options expire worthless? This and six other common options myths debunked). We calculate the trailing twelve month volatility for Systemax, Inc. (considering the last 251 trading day closing values as well as today's price of $22.00) to be 56%. For other call options contract ideas at the various different available expirations, visit the SYX Stock Options page of StockOptionsChannel.com.
The views and opinions expressed herein are the views and opinions of the author and do not necessarily reflect those of Nasdaq, Inc.