Published on: 2026-05-23
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 trades on the stock market, deposit market, and credit market of PJSC “Moscow Exchange MMC-RTS”, approved by the decision of the Supervisory Board dated January 23, 2026 (Protocol No. 11), it has been established that from May 22, 2026, Table 1-O (Only REPO transactions) “Trading modes available for bonds and CCS when concluding transactions in the Stock Market Section and REPO Market Section” of the appendix to the Additional terms for conducting trades on the stock market, approved by Order No. MBC-P-2026-954 dated 16.03.2026 (with amendments and additions) and Order No. MBC-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 | ||
| “REPO with CCB – Targeted Applications” | “REPO with TS – Without “targeted applications” |
“Interdealer REPORT |
|||||
| Permissible calculation codes for individual trading modes | |||||||
| T0/Yn*,Y0/Yn*,Y1/Yn*,Y2/Yn* | Y0/Y1, Y0/Y1W | S0-S2, Rb, Z0 | |||||
| 1 | RU000A10E8W6 | Corporate bond of JSC “Sberbank CIB” | 6-516-01793-A-001P dated 02.02.2026 | RUB, CNY, KZT, BYN | RUB, CNY | – | 1; Permissible are calculation codes that provide for the REP deal term up to 1 trading day |
| 2 | RU000A10EKN2 | Corporate bond of JSC “ALFA-BANK” | 6-917-01326-B-001P from 12.03.2026 | RUB, CNY, KZT, BYN | RUB, CNY | – | 1; The NKD is not calculated; Acceptable are calculation codes that provide for the REPO transaction term up to 1 trading day |
*-The value “n” is defined as follows: https://fs.moex.com/files/20211
1 – Trading is not conducted on the bond redemption date.
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.