Published on: 2026-09-21
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 Board made the following decisions on 21.09.2026:
1. To define:
- 22.09.2026 as the start date of trading during the placement process,
- 09/22/2026 as the date of commencement of trading during circulation after full payment of the following securities
| Name of the security | non-convertible interest (coupon) non-documentary bonds secured by pledge of monetary claims and guarantee |
| Full name of the organization | Limited Liability Company “Specialized Project Financing Society DOM.RF” |
| Type of securities | Corporate bond |
| Registration number from the date of registration | 4-14-00598-R-001P dated 21.05.2026 |
| Nominal value | 1,000 |
| Currency of nominal value | Ruble |
| Number of securities in the issue | 20,000,000 pieces |
| Maturity date | 29.09.2028 |
| Trade Code | RU000A10G643 |
| ISIN code | RU000A10G643 |
| Listing level | First level |
| Sector | Sustainable Development Sector, National and Adaptation Projects Segment |
| Placement method | Open subscription |
| Listing price | 100% of the nominal value |
| Scheduled end date of placement | 30.09.2026 |
| Underwriter | |
| Name | JSC Bank DOM.RF |
| Trading Participant Identifier in the Trading System of PJSC Moscow Exchange | MC0034600000 |
| Short name in the Trading System of PJSC Moscow Exchange | BankDOMRF |
2. Determine:
- 22.09.2026 as the trading start date in the placement process,
- 09/22/2026 as the start date of trading in the circulation process after full payment of the following securities
| Name of the security | Exchange bonds, discounted, non-convertible, uncertificated, series KS-4-1293 |
| Full name of the organization | VTB Bank (public joint-stock company) |
| Type of securities | Exchange-traded bond |
| Registration number from the date of registration | 4B02-1293-01000-B-005P dated 15.07.2026 |
| Nominal value | 1,000 |
| Face value currency | Ruble |
| Number of securities in the issue | 50,000,000 pieces |
| Maturity date | 23.09.2026 |
| Trade code | RU000A10G627 |
| ISIN code | RU000A10G627 |
| Listing level | Third level |
| Placement method | Open subscription |
| Placement price | The issuer’s authorized management body 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 placement | The start date and end date of the placement of exchange-traded bonds coincide. |
| Underwriter | |
| Name | VTB Bank (PJSC) |
| Participant Identifier in the Trading System of PJSC Moscow Exchange | MC0003300000 |
| Short name in the Trading System of PJSC Moscow Exchange | VTB RF |
3. Define:
- 09/22/2026 as the start date of trading in the placement process,
- 22.09.2026 as the date of commencement of trading during the circulation process after full payment of the following securities
| Name of the security | Exchange-traded bonds, interest-bearing, non-convertible, uncertificated series 001P-04 |
| Full name of the organization | Limited Liability Company “Mail.Ru Finance” |
| Type of securities | Exchange-traded bond |
| Registration number from the date of registration | 4B02-04-00566-R-001P dated 21.08.2026 |
| Nominal value | 1,000 |
| Nominal currency value | Ruble |
| Number of securities in the issue | 5,000,000 pieces |
| Maturity date | 06.09.2029 |
| Trade code | RU000A10G635 |
| ISIN code | RU000A10G635 |
| Listing level | Third level |
| Placement method | Open subscription |
| Placement price | 100% of face value |
| Scheduled completion date of placement | 25.09.2026 |
| Underwriter | |
| Name | GPB Bank (JSC) |
| Trading Participant Identifier in the Trading System of PJSC Moscow Exchange | MC0009800000 |
| Short name in the Trading System of PJSC Moscow Exchange | GPB Bank |
Please note; This information is raw content obtained directly from the source of information. It is an accurate report of what the source asserts and does not necessarily reflect the position of MIL-OSI or its clients.