Published on: 2026-07-03
Source: Moscow Exchange –
An important disclaimer is at the bottom of this article.
To the auction participants
We inform you that in accordance with Part I. General Part of the Rules for conducting trading on the stock market, deposit market, and credit market of PJSC Moscow Exchange, approved by the decision of the Supervisory Board of PJSC Moscow Exchange on May 15, 2026 (Protocol No. 17), and Part II. Stock Market Section of the Rules for conducting trading on the stock market, deposit market, and credit market of PJSC Moscow Exchange, approved by the decision of the Supervisory Board of PJSC Moscow Exchange on January 23, 2026 (Protocol No. 11), the following terms, form, and procedure for conducting trading for the buyback of bonds specified in Appendix No. 1 to this Notification (hereinafter – the Bonds) are established:
The trading for the redemption of Bonds will be conducted in the Trading Mode “Redemption: Addressed Orders” in the manner provided in Subsection 1.9 Conducting trading for the acquisition of shares and redemption of bonds of Part II. Trading Rules.
The buyer of the Bonds upon redemption is the Participant of the stock market trades specified in Appendix No. 1 to this Notice.
The size of the standard lot in the trading mode “Buyback: Directed Orders” is set to 1 (one) security.
Appendix No. 1
List of securities for which the terms, form, and procedure for conducting bond buyback trading are determined
| No. p/p | Redemption date | ISIN code of the security issue | Name of the security issue | Name of the auction participant – the securities buyer | Identifier of the trading participant – securities buyer | Additional terms for the acquisition of securities |
| 1 | 08/07/2026 | RU000A0JSGV0 | Corporate Bond 32 of JSC “Russian Railways” | GPB Bank (JSC) | MC0009800000 | Trading hours for the purchase of Bonds:
The purchase price is 100%. |
Please note; This information is raw content obtained directly from the information source. It is an accurate report of what the source claims and does not necessarily reflect the position of MIL-OSI or its clients.