Published on: 2026-06-03
Source: Moscow Exchange –
An important disclaimer is at the bottom of this article.
In accordance with the Listing Rules of PJSC Moscow Exchange, the Chairman of the Management Board on 02.06.2026 adopted the following decisions:
1.Define:
- 03.06.2026 as the start date of trading in the placement process,
- 03.06.2026 as the date of the start of trading in the process of circulation after full payment of the following securities
| Name of the security | Exchange-traded bonds interest non-convertible uncertificated series 002P-02 |
| Full name of the organization | Joint-stock company “ALROSA” (public joint-stock company) |
| Security type | Exchange bond |
| Registration number from the date of registration | 4B02-02-40046-N-002P from 28.05.2026 |
| Nominal value | 1,000 |
| Currency of nominal value | Ruble |
| Number of securities in the issuance | 30,000,000 pieces |
| Maturity date | 18.05.2029 |
| Trade code | RU000A10FAN0 |
| ISIN code | RU000A10FAN0 |
| Listing Level | First level |
| Placement method | Open subscription |
| Placement price | 100% of the nominal value |
| Scheduled completion date of placement | 08.06.2026 |
| Underwriter | |
| Name | OOO VTB Capital Trading |
| Trading Participant Identifier in the Trading System of PJSC Moscow Exchange | MC0569600000 |
| Short name in the Trading System of PJSC Moscow Exchange | VTB Capital |
2.Determine:
- 03.06.2026 as the start date of trading during the placement process,
- 03.06.2026 as the start date of trading in the process of circulation after full payment of the following securities
| Name of the security | Exchange-traded discounted non-convertible bearer bond series KS-4-1215 |
| Full name of the organization | VTB Bank (public joint-stock company) |
| Type of security | Exchange bond |
| Registration number from the registration date | 4B02-1215-01000-B-005P from 30.04.2026 |
| Nominal value | 1,000 |
| Currency of nominal value | The Republic |
| Number of securities in the issue | 100,000,000 pieces |
| Maturity date | 06/04/2026 |
| Trade code | RU000A10FAJ8 |
| ISIN code | RU000A10FAJ8 |
| Listing level | Third level |
| Placement method | Open subscription |
| Placement price | The authorized body of the issuer’s management makes a decision on the placement price before the start of the placement of exchange bonds. The placement price is uniform for all purchasers of exchange bonds. |
| Scheduled end date of placement | The start date and end date of the listing of exchange-traded bonds coincide. |
| Underwriter | |
| Name | VTB Bank (PJSC) |
| Trader Identifier in the Trading System of PJSC Moscow Exchange | MC0003300000 |
| Short name in the Trading System of PJSC Moscow Exchange | VTB RF |
3.Define:
- 03.06.2026 as the start date of trading in the placing process,
- 03.06.2026 as the trading start date in the course of circulation of the following securities
| Name of the security | Federal loan bonds with a fixed coupon yield |
| Full name of the organization | Ministry of Finance of the Russian Federation |
| Security type | Federal loan bond |
| Registration number from the date of registration | 12156124V from 01.06.2026 |
| Nominal value | 10,000 |
| Currency of nominal value | Chinese yuan |
| Number of securities in issue | 1,000,000 pieces |
| Maturity date | 21.05.2036 |
| Trade Code | RU000A10FAK6 |
| ISIN code | RU000A10FAK6 |
| Listing level | First level |
| Method of placement | Closed subscription |
| Placement price | 100 % of the nominal value |
| Scheduled completion date of placement | 30.06.2026 |
| Underwriter | |
| Name | GPB Bank (JSC) |
| Participant identifier in the trading system of PJSC Moscow Exchange | MC0009800000 |
| Short name in the Trading System of PJSC Moscow Exchange | GPB Bank |
4.Define:
- 03.06.2026 as the trading start date in the placement process,
- 03.06.2026 as the date of the start of trading in the process of circulation after full payment of the following securities
| Name of the security | Exchange-traded interest non-convertible bearer bond series 001P-01 |
| Full name of the organization | Limited Liability Company “INNOVATIVE FIRE SAFETY SYSTEMS” |
| Type of security | Exchange-traded bond |
| Registration number from the date of registration | 4B02-01-00278-L-001P from 29.05.2026 |
| Nominal value | 1,000 |
| Currency of nominal value | Rubles |
| Number of securities in issue | 300,000 pieces |
| Maturity date | 18.05.2029 |
| Trade code | RU000A10FAL4 |
| ISIN code | RU000A10FAL4 |
| Listing level | Third level |
| Placement method | Open subscription |
| Placement price | 100% of the nominal value |
| Scheduled end date of placement | 08.06.2026 |
| Underwriter | |
| Name | GPB Bank (JSC) |
| Trader Identifier in the Trading System of PJSC Moscow Exchange | MC0009800000 |
| Short name in the Trading System of PJSC Moscow Exchange | GPB Bank |
5.Define:
- 03.06.2026 as the date of the start of trading in the process of placement,
- 03.06.2026 as the date of the start of trading in the process of circulation after full payment of the following securities
| Name of the security | Exchange-traded non-convertible interest-bearing uncertificated bond series PBO-002R-K717 |
| Full name of the organization | State Development Corporation “VEB.RF” |
| Security type | Exchange bond |
| Registration number from the date of registration | 4B02-278-00004-T-002P dated 20.03.2026 |
| Nominal value | 1,000 |
| Currency of nominal value | Subl |
| Number of securities in issue | 50,000,000 pieces |
| Maturity date | 17.06.2026 |
| Trade code | RU000A10EPJ9 |
| ISIN code | RU000A10EPJ9 |
| Listing level | Third level |
| Placement Method | Open subscription |
| Placement price | 100% of the nominal value |
| Scheduled end date of placement | 06/05/2026 |
| Underwriter | |
| Name | WEB.RF |
| Trader Identifier in the Trading System of PJSC Moscow Exchange | MC0046000000 |
| Short name in the Trading System of PJSC Moscow Exchange | WEB RF |
Please note; This information is raw content obtained directly from the information source. It represents an exact report of what the source claims and does not necessarily reflect the position of MIL-OSI or its clients.