Published on: 2026-05-05
Source: Moscow Exchange – Московская Биржа –
An important disclaimer is at the bottom of this article.
To the participants of the trades
We inform you that on the basis of a letter from the Bank of Russia and in accordance with Part I. General Part and Part II. Stock Market Section of the Rules for Conducting Trading on the Stock Market, the Deposit Market and the Credit Market of PJSC Moscow Exchange, the forms, time, term and procedure for conducting auctions for placement and trading of the following federal loan bonds have been established by order:
1.
| Name of the Issuer | Ministry of Finance of the Russian Federation |
| Name of the security | Federal loan bonds with a fixed coupon income |
| State registration number of issue | 26235RMFS of 12.10.2020 |
| Дата проведения аукциона | May 6, 2026 |
| Information about placement (Trading mode, placement form) | The placement of Bonds will be carried out in the trading mode “Placement: Auction” by holding an Auction to determine the placement price. BoardId: PACT (Calculations: rubles) |
| Trade code | SU26235RMFS0 |
| ISIN code | RU000A1028E3 |
| Calculation code | B01 |
| Additional placement terms |
|
| Trading time | Trading hours:
|
2.
| Name of the Issuer | Ministry of Finance of the Russian Federation |
| Name of the security | Federal loan bonds with a fixed coupon yield |
| State registration number of the issue | 26240RMFS from 28.06.2021 |
| Date of the auction | May 6, 2026 |
| Information about placement (Trading mode, placement form) | The placement of bonds will be carried out in the trading mode “Placement: Auction” by conducting an auction to determine the placement price. BoardId: PACT (Calculations: Rubles) |
| Trade code | SU26240RMFS0 |
| ISIN code | RU000A103BR0 |
| Calculation code | B01 |
| Additional placement conditions |
|
| Trading time | Trading time:
|
Please note; this information is raw content obtained directly from the source of the information. It is a precise report of what the source asserts and does not necessarily reflect the position of MIL-OSI or its clients.