/EINPresswire.com/ -- TORONTO, ONTARIO -- (Marketwired) -- 03/23/16 -- Top 10 Split Trust (the "Fund") (TSX: TXT.UN) (TSX: TXT.PR.A) has announced that the Fund will effect a partial redemption of its preferred securities ("Preferred Securities") in order to maintain an equal number of Preferred Securities and capital units ("Capital Units") of the Fund outstanding. The partial redemption of the Preferred Securities is being made in connection with the automatic five-year extension of the term of the Fund to March 31, 2021 that was approved by unitholders back on March 21, 2011.

Pursuant to the special retraction right granted to Security holders in connection with the extension of Fund, 125,696 Preferred Securities and 137,494 Capital Units were surrendered for retraction. In order to maintain an equal number of Preferred Securities and Capital Units, the Fund will redeem an aggregate of 11,798 Preferred Securities on a pro rata basis from all holders of record of Preferred Securities on March 31, 2016 (the "Repayment Date), representing approximately 0.9% of the 1,332,821 issued and outstanding Preferred Securities (pre-Special Retraction Right). Each Preferred Security that is redeemed pursuant to the partial redemption will be redeemed at a price equal to $12.50, being the principal amount per Preferred Security, plus all accrued and unpaid interest thereon (the "Repayment Price"). The Repayment Price will be paid to holders whose Preferred Securities are redeemed by the Fund within 10 business days following the Repayment Date.

John Germain, Senior Vice-President, CFO

Contacts:
Strathbridge Asset Management Inc.
Investor Relations
416.681.3966 or Toll Free: 1.800.725.7172
www.strathbridge.com

Legal Disclaimer:

EIN Presswire provides this news content "as is" without warranty of any kind. We do not accept any responsibility or liability for the accuracy, content, images, videos, licenses, completeness, legality, or reliability of the information contained in this article. If you have any complaints or copyright issues related to this article, kindly contact the author above.