Published on: 2026-09-08
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 07.09.2026 made the following decisions:
1. Determine:
- September 8, 2026 as the date of the start of trading in the placement process,
- 08.09.2026 as the trading start date during the circulation process after full payment of the following securities
| Name of the security | Exchange-traded discounted non-convertible non-documentary bonds of series KS-4-1283 |
| Full legal name of the organization | VTB Bank (public joint-stock company) |
| Type of securities | Exchange-traded bond |
| Registration number from the date of registration | 4B02-1283-01000-B-005P dated 15.07.2026 |
| Nominal value | 1,000 |
| Currency of nominal value | Ruble |
| Number of securities in the issue | 50,000,000 pieces |
| Maturity date | 09.09.2026 |
| Trade code | RU000A10G0T7 |
| ISIN code | RU000A10G0T7 |
| Listing level | Third level |
| Placement method | Open subscription |
| Placement price | The authorized management body of the issuer makes the 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 bonds coincide. |
| Underwriter | |
| Name | VTB Bank (PJSC) |
| Trading Participant Identifier in the Trading System of PJSC Moscow Exchange | MC0003300000 |
| Short name in the Trading System of PJSC Moscow Exchange | VTB Russia |
2. Define:
- 08.09.2026 as the start date of trading during the placement process,
- 08.09.2026 as the date of commencement of trading during circulation after full payment of the following securities
| Name of the security | Exchange bonds with collateral, interest-bearing, non-convertible, non-documentary series 003P-07 |
| Full name of the organization | Limited Liability Company “EvrazHolding Finance” |
| Type of securities | Exchange bond |
| Registration number from the date of registration | 4B02-07-36383-R-003P dated 02.09.2026 |
| Nominal value | 1,000 |
| Currency of the nominal value | Ruble |
| Number of securities in the issue | 23,000,000 pieces |
| Maturity date | 25.05.2029 |
| Trade code | RU000A10G0W1 |
| ISIN code | RU000A10G0W1 |
| Listing level | Second level |
| Placement method | Open subscription |
| Placement price | 100% of the nominal value |
| Scheduled end date of placement | 11.09.2026 |
| Underwriter | |
| Name | PJSC Sovcombank |
| Participant Identifier in the Trading System of PJSC Moscow Exchange | MC0253800000 |
| Short name in the Moscow Exchange PJSC Trading System | Sovcombank |
3. Define:
- 08.09.2026 as the start date of trading during the placement process,
- 08.09.2026 as the date of commencement of trading in the process of circulation after full payment of the following securities
| Name of the security | non-convertible bearer bonds with interest secured by cash claims of class “A” |
| Full name of the organization | Limited Liability Company “Specialized Financial Society Svoy Kapital – Fintech” |
| Type of securities | Corporate bond |
| Registration number from the date of registration | 4-01-01004-R dated 27.07.2026 |
| Nominal value | 1,000 |
| Nominal value currency | Ruble |
| Number of securities in the issue | 1,000,000 pieces |
| Maturity date | 25.07.2032 |
| Trade code | RU000A10G0Z4 |
| ISIN code | RU000A10G0Z4 |
| Listing Level | Third level |
| Placement method | Open subscription |
| Placement price | 100% of the nominal value |
| Scheduled end date of placement | 11.09.2026 |
| Underwriter | |
| Name | PJSC Sovcombank |
| Trading Participant Identifier in the PJSC Moscow Exchange Trading System | MC0253800000 |
| Short name in the trading system of PJSC Moscow Exchange | Sovcombank |
Please note; This information is raw content obtained directly from the information source. It represents an accurate report of what the source claims and does not necessarily reflect the position of MIL-OSI or its clients.