Channel
@ProArbitrationRu
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
141subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001295419714 |
|---|---|
| Type | Channel |
| Username | @ProArbitrationRu |
| Description | Litigation and arbitration in Russia. by Mikhail Samoylov, LL.M. (MIDS). 📨 @MSMContact_bot |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/ProArbitrationRu |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 22:01 | 141 | no change |
| 8 Aug 2026, 17:31 | 141 | first reading |
20 posts held, back to 25 April 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 4 of 7 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 20 (25 April 2026 – 7 August 2026) |
| Views total | 634 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 22:01 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
9 reactions across 7 posts, in 2 distinct kinds. The most used accounts for 77.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7 | 77.8% | |
| 👍 | 2 | 22.2% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 8 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 9reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 25 April 2026 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🇷🇺 🇳🇬 𝗥𝘂𝘀𝘀𝗶𝗮𝗻 𝗖𝗼𝘂𝗿𝘁 𝗥𝗲𝗳𝘂𝘀𝗲𝘀 𝗘𝗻𝗳𝗼𝗿𝗰𝗲𝗺𝗲𝗻𝘁 𝗼𝗳 𝟮𝟬𝟬𝟴 𝗡𝗶𝗴𝗲𝗿𝗶𝗮𝗻 𝗝𝘂𝗱𝗴𝗺𝗲𝗻𝘁 𝗮𝘀 𝗧𝗶𝗺𝗲-𝗕𝗮𝗿𝗿𝗲𝗱. In Case No. A40-37908/2024, a Russian court, by its decision dated 31 July 2026, refused recognition and enforcement of a court judgment issued by a Nigerian court in 2008. The court held that the application for recognition had been filed after expiry of the time limit for such an application. Article 246 of the Russian Arbitrazh Proce…
👍1
𝗥𝘂𝘀𝘀𝗶𝗮𝗻 𝗖𝗼𝘂𝗿𝘁 𝗘𝗻𝗳𝗼𝗿𝗰𝗲𝘀 𝗜𝗖𝗖 𝗔𝘄𝗮𝗿𝗱, 𝗥𝗲𝗷𝗲𝗰𝘁𝘀 𝗣𝘂𝗯𝗹𝗶𝗰 𝗣𝗼𝗹𝗶𝗰𝘆 𝗮𝗻𝗱 𝗦𝗮𝗻𝗰𝘁𝗶𝗼𝗻𝘀 𝗢𝗯𝗷𝗲𝗰𝘁𝗶𝗼𝗻𝘀. In Case No. A60-26002/2026, a decision dated 24 July 2026, a Russian court issued a writ of execution for an ICC arbitral award rendered in an arbitration seated in Moscow and held: 1. An assignment of a claim under a foreign trade supply contract from a Dutch assignor to a Russian assignee does not, in itself, violate Russian public p…
❤1
𝐋𝐚𝐰𝐲𝐞𝐫 𝐅𝐢𝐧𝐞𝐝 𝐟𝐨𝐫 𝐔𝐬𝐢𝐧𝐠 𝐀𝐈. A court decision, in Russian, dated 2 July 2026, in Case No. A45-5305/2023, is another one in which a lawyer was fined for contempt of court — the lawyer cited court decisions that had never existed and were allegedly hallucinated by AI. 🤖 ProArbitration.Ru ✈
𝗗𝗼 𝘀𝗮𝗻𝗰𝘁𝗶𝗼𝗻𝘀 𝗼𝘃𝗲𝗿𝗿𝗶𝗱𝗲 𝗮𝗿𝗯𝗶𝘁𝗿𝗮𝘁𝗶𝗼𝗻 𝗰𝗹𝗮𝘂𝘀𝗲𝘀 𝗶𝗻 𝗥𝘂𝘀𝘀𝗶𝗮? 𝗟𝗶𝗸𝗲𝗹𝘆 '𝘆𝗲𝘀,' 𝗯𝘂𝘁 𝘁𝗵𝗲𝗿𝗲 𝗶𝘀 𝗻𝗼 𝘀𝘁𝗿𝗮𝗶𝗴𝗵𝘁 𝗹𝗶𝗻𝗲 𝘁𝗼 𝘁𝗵𝗲 𝗮𝗻𝘀𝘄𝗲𝗿 𝘀𝗼 𝗳𝗮𝗿. In Case No. A56-113018/2025, a Russian entity, disregarding an LMAA arbitration clause, brought a legal action against two Russian entities. By its ruling dated 28 May 2026, the court of first instance referred the parties to the agreed forum. The court held that (1) the claimant was not listed on a…
❤1
🤖 𝗙𝗶𝗿𝗲𝗱 𝗼𝘃𝗲𝗿 𝗗𝗲𝗲𝗽𝗦𝗲𝗲𝗸 𝗱𝗮𝘁𝗮 𝘂𝗽𝗹𝗼𝗮𝗱. It seems that the case of Remizova v. EnergoPof LLC is the first case in Russia in which an employee was fired, among other reasons, for uploading confidential information to DeepSeek. The court of first instance's judgment dated 26 May 2026, in Russian, is attached. ProArbitration.Ru ✈
❤1
🇷🇺🇹🇷🇨🇭𝗥𝘂𝘀𝘀𝗶𝗮𝗻 𝗖𝗼𝘂𝗿𝘁 𝗨𝗽𝗵𝗼𝗹𝗱𝘀 𝗟𝗖𝗜𝗔 𝗔𝗿𝗯𝗶𝘁𝗿𝗮𝘁𝗶𝗼𝗻. In Case No. A56-24342/2025, by decision dated 17 July 2026, a Russian court refused a motion brought by a Russian company to restrain a Turkish company and a Swiss company from pursuing its claims in LCIA arbitration. The court held that the Russian company had neither been included on any sanctions lists nor was the dispute under arbitration arising out of unilateral san
🇷🇺🇸🇬 A Russian court, by its ruling dated 8 July 2026 (Case No. A40-20468/2024), has granted an application to reconsider its ruling dated 2 October 2024 on the recognition and enforcement in Russia of a USD 500 million SIAC award against Petrovietnam. The court granted reconsideration on the ground of newly discovered circumstances, namely the Singapore Court of Appeal's judgment in [2025] SGCA 50. 📆 A hearing is …
In Case No. А56-24289/2025, by a decision dated 19 June 2026, a Russian court left without consideration an action brought by VTB Bank against JPMorgan Chase Bank on the ground that the parties to the dispute had concluded an arbitration agreement. Recently, an English court granted an anti-suit injunction (ASI) restraining VTB Bank from pursuing its claim before the Russian court (see [2025] EWHC 1368 (Comm)). Had…
In Case No. A40-332538/25-68-2153, a Russian court issued a decision on 15 May 2026 recognising and enforcing an ICC award in 🇷🇺 Russia. The ICC award had been rendered in favour of a 🇸🇬 Singapore-based company against a 🇰🇷 South Korean company. The Russian court also ordered the award debtor to pay a court-imposed fine of RUB 10,000 for each seven-day period of non-compliance if the award debtor failed to comply wi…
Can the English courts grant an injunction restraining proceedings brought in a foreign court under the New York Convention? This issue is to be decided by the UK Supreme Court. The hearing is scheduled for 15–16 June 2026. 🔗 https://supremecourt.uk/cases/uksc-2025-0150 ProArbitration.Ru ✈
𝑳𝒊𝒎𝒊𝒕𝒆𝒅 𝑳𝒊𝒂𝒃𝒊𝒍𝒊𝒕𝒚 𝑪𝒐𝒎𝒑𝒂𝒏𝒚 “𝑬𝒖𝒓𝒐𝑪𝒉𝒆𝒎 𝑵𝒐𝒓𝒕𝒉-𝑾𝒆𝒔𝒕-2” 𝒗. 𝑻𝒆𝒄𝒏𝒊𝒎𝒐𝒏𝒕 𝑺.𝑷.𝑨. 🇮🇳🇷🇺 The Bombay High Court held that, at the pre-trial stage, the Russian judgment could not be regarded as conclusive. The Court also found that the jurisdiction of the Arbitrazh Court of the City of Moscow was doubtful in light of the arbitration agreements and the pending international arbitration. 🔗 Attached is the judgment dated 8 June 2026.
❤2
In the recent Case No. А21-4252/2026 (RUSAL v. OWH SE i.L.), a Russian court held that either party to an arbitration — whether the award creditor or the award debtor — may seek recognition and enforcement of an arbitral award before a court. I wonder whether this approach is inconsistent with the 1958 New York Convention, or whether it falls within Article IV, given that the provision refers only to “the party appl…
Showing the 12 most recent of 20 posts we hold for @ProArbitrationRu. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Citation-graph rank — 594,440 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 8 August 2026 — this entry's latest reading, not the date you are reading this.
“ProArbitration.Ru” (@ProArbitrationRu), 141 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/ProArbitrationRu.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.