Published on: 2026-05-19
Source: Moscow Exchange –
An important disclaimer is at the bottom of this article.
To the participants of the trades
We inform you that, in accordance with Part I. General Part of the Rules for conducting trading on the stock market, the deposit market, and the credit market of the PJSC “Moscow Exchange MICEX-RTS”, approved by the decision of the Supervisory Board on January 23, 2026 (Protocol No. 11), it has been established that from May 18, 2026, Table 1-O (Only REPO transactions) “Trading modes available for bonds and CCUs when concluding transactions in the Stock Market Section and the REPO Market Section” of the appendix to the Additional Terms for conducting trading on the stock market, approved by Order No. MBI-P-2026-954 dated 16.03.2026 (with amendments and additions) and Order No. MBI-P-2026-1010 dated 18.03.2026.(with changes and additions), will be supplemented with the following content lines:
| № | Trading code | Name | Registration number | Conducting trades | Features | ||
| “REP with CSC – Targeted Applications” | “REPO with the CEC – Without “address applications” |
“Interdealer REPOST |
|||||
| Permissible calculation codes for individual trading modes | |||||||
| T0/Yn*,Y0/Yn*,Y1/Yn*,Y2/Yn* | Y0/Y1,Y0/Y1W | S0-S2, Rb, Z0 | |||||
| 1 | RU000A10F2F3 | Corporate bond of JSC “Sberbank KIB” | 6-642-01793-A-001P of 22.04.2026 | RUB, CNY, KZT, BYN | RUB, CNY | – | 1; Permissible are calculation codes that provide for a REPO transaction term of up to 1 trading day |
| 2 | RU000A10CYX6 | Corporate bond of JSC “Sberbank CIB” | 6-382-01793-A-001P from 25.09.2025 | RUB, CNY, KZT, BYN | RUB, CNY | – | 1; Acceptable are calculation codes that provide for the term of a REPO transaction of up to 1 trading day |
*-The meaning of “n” is defined as follows: https://fs.moex.com/files/20211
1 – Trading is not conducted on the bond maturity date.
Please note; This information is raw content obtained directly from the source. It represents an accurate report of what the source claims and does not necessarily reflect the position of MIL-OSI or its clients.