Published on: 2026-08-15
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 made the following decisions on 14.08.2026:
1. Define:
- 17.08.2026 as the start date of trading during the placement process,
- 17.08.2026 as the start date of trading in the market after full payment of the following securities
| Name of the security | structured bonds with interest, discount, non-documentary, non-convertible, secured, series CIB-SN-INDFX-001S-491 |
| Full name of the organization | Joint Stock Company “Sberbank CIB” |
| Type of securities | Corporate bond |
| Intended for qualified investors | Yes |
| Registration number from the date of registration | 6-491-01793-A-001P dated 21.11.2025 |
| Nominal value | 1,000 |
| Currency of the nominal value | Ruble |
| Number of securities in the issue | 1,000,000 pieces |
| Maturity date | 24.08.2027 |
| Trade code | RU000A10DNB3 |
| ISIN code | RU000A10DNB3 |
| Listing level | Third level |
| Placement method | Closed subscription |
| Posting price | 100% of the face value |
| Scheduled end date of placement | 18.08.2026 |
| Underwriter | |
| Name | JSC “Sberbank CIB” |
| Participant Identifier in the Trading System of PJSC Moscow Exchange | MC0005500000 |
| Short name in the PJSC Moscow Exchange Trading System | Sberbank CIB |
2. Define:
- 17.08.2026 as the trading start date in the placement process,
- August 17, 2026 as the date of commencement of trading during the circulation process after full payment of the following securities
| Name of the security | structured interest-bearing discount bearer non-convertible bonds with collateral security of series CIB-SN-INDFX-001S-492 |
| Full name of the organization | Joint Stock Company “Sberbank CIB” |
| Type of securities | Corporate bond |
| Intended for qualified investors | Yes |
| Registration number from the date of registration | 6-492-01793-A-001P dated 21.11.2025 |
| Nominal value | 1,000 |
| Currency of nominal value | Ruble |
| Number of securities in the issue | 1,000,000 pieces |
| Maturity date | 26.11.2029 |
| Trade Code | RU000A10DNC1 |
| ISIN code | RU000A10DNC1 |
| Listing Level | Third level |
| Placement method | Closed subscription |
| Placement price | 100% of the nominal value |
| Scheduled end date of placement | 18.08.2026 |
| Underwriter | |
| Name | JSC “Sberbank CIB” |
| Participant Identifier in the Trading System of PJSC Moscow Exchange | MC0005500000 |
| Short name in the Trading System of PJSC Moscow Exchange | Sberbank CIB |
3. Define:
- 17.08.2026 as the start date of trading during the placement process,
- 17.08.2026 as the date of the start of trading during circulation after full payment of the following securities
| Name of the security | Exchange bonds, discount, non-convertible, uncertificated, series KS-4-1267 |
| Full name of the organization | VTB Bank (public joint-stock company) |
| Type of securities | Exchange bond |
| Registration number and date of registration | 4B02-1267-01000-B-005P dated 15.07.2026 |
| Nominal value | 1,000 |
| Nominal value currency | Ruble |
| Number of securities in the issue | 100,000,000 pieces |
| Maturity date | 18.08.2026 |
| Trade code | RU000A10FVK2 |
| ISIN code | RU000A10FVK2 |
| Listing level | Third level |
| Method of placement | Open subscription |
| Placement price | The authorized management body of the issuer 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 the 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 Russia |
Please note; This information is raw content obtained directly from the source. It is an accurate report of the claims made by the source and does not necessarily reflect the position of MIL-OSI or its clients.