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, non-convertible interest-bearing, uncertificated series 002P-02 |
| Full name of the organization | Joint-stock company “ALROSA” (public joint-stock company) |
| Type of security | Exchange bond |
| Registration number from the registration date | 4B02-02-40046-N-002P dated 28.05.2026 |
| Nominal value | 1,000 |
| Currency of nominal value | Sub |
| Number of securities in the issue | 30,000,000 pieces |
| Maturity date | 18.05.2029 |
| Trade code | RU000A10FAN0 |
| ISIN code | RU000A10FAN0 |
| Listing level | Первый уровень |
| Method of placement | Open subscription |
| Placement price | 100% of the nominal value |
| Scheduled end date of posting | 08.06.2026 |
| Underwriter | |
| Name | OOO VTB Capital Trading |
| Trader Identifier in the Trading System of PJSC Moscow Exchange | MC0569600000 |
| Short name in the Trading System of PJSC Moscow Exchange | VTB Capital Trade |
2.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 during the circulation process after full payment of the following securities
| Name of the security | Exchange-traded discount 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 | Rubles |
| 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-traded bonds. The placement price is uniform for all purchasers of exchange-traded bonds. |
| Scheduled end date of posting | The start date and the end date of bond listing 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 trading start date in the listing process,
- 03.06.2026 as the start date of trading during the 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 |
| Type of security | Federal loan bond |
| Registration number from the registration date | 12156124V from 01.06.2026 |
| Nominal value | 10,000 |
| Currency of nominal value | Chinese yuan |
| Number of securities in the 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 end date of posting | 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 start date of trading in the placement process,
- 03.06.2026 as the start date of trading during the circulation process after full payment of the following securities
| Name of the security | Exchange-traded non-convertible interest-bearing bearer bonds series 001P-01 |
| Full name of the organization | Limited Liability Company “INNOVATIVE SYSTEMS OF FIRE SAFETY” |
| Type of security | Exchange bond |
| Registration number from the date of registration | 4B02-01-00278-L-001P dated 29.05.2026 |
| Nominal value | 1,000 |
| Currency of nominal value | Sub |
| Number of securities in issuance | 300,000 pieces |
| Maturity date | 18.05.2029 |
| Trade Code | RU000A10FAL4 |
| ISIN code | RU000A10FAL4 |
| Listing level | Third level |
| Method of placement | Open subscription |
| Placement price | 100% of the nominal value |
| Scheduled end date of posting | 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.Determine:
- 03.06.2026 as the start date of trading in the placement process,
- 03.06.2026 as the date of the start of trading during the circulation process after full payment of the following securities
| Name of the security | Exchange-traded bonds, interest non-convertible, non-documentary series PBO-002R-K717 |
| Full name of the organization | State Corporation for Development “VEB.RF” |
| Type of security | Exchange bond |
| Registration number from the date of registration | 4B02-278-00004-T-002P from 20.03.2026 |
| Nominal value | 1,000 |
| Currency of nominal value | Рубль |
| Number of securities in the issue | 50,000,000 pcs |
| 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 completion date of placement | 06/05/2026 |
| Underwriter | |
| Name | WEB.RF |
| Participant 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, directly obtained from the source of the information. It represents an accurate report of what the source claims and does not necessarily reflect the position of MIL-OSI or its clients.